Issue Details (XML | Word | Printable)

Key: JRA-12165
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Mario Giacomino [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Unclear error message when bulk moving issues whose reporter cannot create issues

Created: 12/Feb/07 06:49 PM   Updated: 01/Jul/08 09:40 PM
Component/s: Bulk Operations
Affects Version/s: 3.7.2
Fix Version/s: 3.13.x

Time Tracking:
Original Estimate: 4 days
Original Estimate - 4 days
Remaining Estimate: 4 days
Remaining Estimate - 4 days
Time Spent: Not Specified
Remaining Estimate - 4 days

File Attachments: None
Image Attachments:

1. bulkmove_reporter.png
(58 kB)
Issue Links:
Reference
 

Participants: Anton Mazkovoi [Atlassian], Jed Wesley-Smith [Atlassian] and Mario Giacomino [Atlassian]
Since last comment: 39 weeks, 3 days ago
To be done by: Pair of developers
Labels:


 Description  « Hide
When users leave the organization, we recommend that they be removed from JIRA groups as a means of revoking their access. If the JIRA admin then wants to bulk-move a removed user's issues, JIRA fails with a cryptic error:

This field cannot be updated, its value will be set to the default for the field in the target environment.

We should either print a more useful error message, or modify the code to allow this operation.

See the thread at:

http://forums.atlassian.com/thread.jspa?forumID=46&threadID=11054



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jed Wesley-Smith [Atlassian] added a comment - 06/Dec/07 08:00 PM
The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.