Issue Summary

For example, associating a new issue type to an existing workflow scheme that applies to 2,000 projects has been observed to take days to complete

Steps to Reproduce

• Have a workflow scheme that applies to 2,000 projects
• Associate new issue type to this workflow scheme
  • 
• Confirm
  • 
• Timeout and error occurs as the initial progress URL includes 2,000 project ids which exceeds the URL limit of Tomcat, see HAR file
• Removing 2,000 project id parameters from the URL allows progress to be seen: http://10.125.90.70/jira/secure/project/SelectProjectWorkflowSchemeStep3.jspa?taskId=10700&draftMigration=true&schemeId=10103
  • 
• After an hour the workflow migration tasks was working on projects starting with AC*, about 2% complete

Expected Results

• Workflow scheme modifications should never take more than a few hours, even if they apply to a large amount of projects.
• Attempting to view progress should not result in an error

Actual Results

• We have reports of associating a new issue type to an existing workflow scheme taking 2 weeks to complete
• Viewing progress of a workflow scheme modification requires shortening the URL

add-issuetype-journey.har

Workaround

While the background process can take a long time to complete it is not resource intensive and will not cause performance issues. Do not restart Jira until this process completes however