-
Type:
Suggestion
-
Resolution: Won't Do
-
Component/s: None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
When an error occurs during a Bulk move operation, the following error is shown in the UI:
Error while updating selected issues. Please refer to the log for more detail
and the following error is shown in the logs.
2013-04-21 09:01:00,251 TP-Processor8 INFO username 541x789x1 10zbyef /secure/views/bulkedit/BulkMigratePerform.jspa [jira.bulkedit.operation.BulkMigrateOperation] Performing move for project Project Name issue type: Bug 2013-04-21 09:01:00,327 TP-Processor8 ERROR username 541x789x1 10zbyef /secure/views/bulkedit/BulkMigratePerform.jspa [jira.bulkedit.operation.BulkMoveOperationImpl] An exception occured while moving 'KEY-1234' : No step associated with status In QA in new workflow jira. Rolling back the operation 2013-04-21 09:01:00,330 TP-Processor8 ERROR username 541x789x1 10zbyef /secure/views/bulkedit/BulkMigratePerform.jspa [action.issue.bulkedit.BulkMigrate] Error while performing Bulk Edit operation. java.lang.RuntimeException: No step associated with status In QA in new workflow jira
This information should be visible to the user performing the operation, so they can solve this on their own, rather than having to contact their admin to get to the logs.
This is especially for OnDemand where only Atlassian has access to the logs.
- is related to
-
JRASERVER-32730 Errors during bulk move should be displayed in the UI and not just the logs
- Closed