Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.
Testing Notes
Q: Who has permission to simplify the workflow? Board owner or admin?
A: 
Admin or Sys Admin
Q: If board owner is allowed, what if they don't have permissions to edit the workflow of the project?
A: N/A
Q: What if a simplified workflow already exists for this project?
A: Dialog prompt is not given.
Q: What about the resolve screen or modal dialogs from the last workflow?
A: All screens from previous workflow are removed.
Q: What will happen if the user is logged out/migration is interrupted during migration?
A: We now make one call to the server via REST, to both create the new (simplified) workflow scheme and to kick off the migration of the workflow.
Q: What if an issue is being transitioned during migration?
A: Whatever happens in JIRA will happen here.
Q: What if the user's security token is expired?
A: The XSRF token will no longer be used in this operation.
Q: What if the board filter is changed to include multiple projects when at the workflow migration dialog?
A: I'm assuming it will fail with an error.
- Deploying a fresh JIRA 5.0.7 instance equipped with GreenHopper 6.0.2, tried to enable the Simplify Workflow button but it failed with the following error:
- After that, authenticate as a user with the Administrator Access:
- After that, the workflow migration works fine:
It would be useful if there is some sort of indication that shows the user does not have the Administrator Access. Perhaps next to the Simplify Workflow button.
Workaround to this issue: Simplified Workflow button fails with "Workflow Migration did not complete successfully"
Attachments
Issue Links
- is duplicated by
-
JSWSERVER-5905 Custom Workflow error when converting to Simplified Workflow
-
- Closed
-
- relates to
-
- Closed