-
Bug
-
Resolution: Fixed
-
High
-
18
-
Severity 3 - Minor
-
33
-
-
Issue Summary
Changing workflow that impacts large number of issues, causes issues created during workflow migration in an invalid workflow state. These new tickets created during the migration window still points to the old workflow. Trying to transition the issue fails with the error ‘Couldn't find the workflow’
Steps to Reproduce
- Go to Project Settings -> Workflows and change the workflow for any issue type.
- Pre-requisite: Make sure the project has more number of tickets under that specific issue type, so that the workflow migration takes a few minutes/hours.
- While the workflow migration happens, open a few fresh tickets in the same issue type.
Expected Results
The new tickets should start using the new workflow. We should be able to transition the tickets properly.
Actual Results
The new tickets still points to the old workflow. We’re unable to transition the tickets, it fails with the error ‘Couldn't find the workflow’.
Workaround
- Move the ticket to a different issue type, and then revert it back to the original issue type. This would trigger workflow changes and it will fix the problem.
- Make a copy of the new workflow, and re-associate it to the issue type again. This would trigger the workflow migration again, and the problematic tickets will be fixed as a part of it. However, this operation might again take some time (based on the size of your project).
- is duplicated by
-
JRACLOUD-66707 Modifying Workflow Scheme attached to many projects causes Zombie task
-
- Closed
-
- is related to
-
JRACLOUD-79930 Preserve Workflow Scheme ID after editing workflows in the scheme, where the scheme is shared by multiple projects
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Hey everyone,
We have completed roll out.