Consequence of migrating to the new JIRA flow
The JIRA process for each kind of issue type is controlled by a set of flows, i.e workflows. In order to migrate to the new JIRA flow, all current issues must be migrated to the new versions of these workflows.
All issue status must also be migrated to their counterpart in the JIRA flow.
Workflow migration
Currently all main tasks – change requests, bugs and bugs (non-production) – are utilizing the CDRator Main task workflow. This workflow will be substituted by the new main flow; the CDRator Workflow Main-Task 4.1 workflow.
Migration of the main workflow
The following table gives an overview of which workflow states that maps to each other in the new and old workflow.
Current state |
New state |
Migration comment |
|---|---|---|
Open |
Open |
|
Analyzing |
Analyzing |
|
Ready for processing |
Ready for processing |
|
In progress |
In progress |
|
On hold |
On hold |
|
Waiting |
On hold |
|
In QA |
In QA |
|
Resolved |
Ready for release |
|
Delivered |
Resolved |
|
Reopened |
Open |
Instead of reopening a task, a clone must be created. |
Closed |
Closed |
Migrated issues will be closed as accepted |