-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
None
-
3
-
Severity 2 - Major
Issue Summary
Issue status duplication due to server side configuration change. This leads to migration failures.
Steps to Reproduce
- By default the issue status on the server, 'To Do', is mapped to the category 'To Do'. (Status Category number 2).
- On cloud the status, 'To Do', doesn't exist by default.
- I migrate a project for the first time to the cloud instance and this leads to creation of the issue status 'To Do' on the cloud [To Do ----> To Do].
- On the server, I will change the issue status category of 'To Do' ---> 'In Progress'.
- I will perform a migration of another project and this creates a duplicate for the status, 'To Do(migrated)'.
- Irrespective of the creation of duplicate status, the migration still fails with similar error below.
2021-03-22 12:28:28.053 ERROR MACS project-import We couldn't import Issue MACS-1. Reason: NullPointerException: There is no step in workflow [Software Simplified Workflow for Project MACS] linked to status [To Do (migrated)]. This caused 4 other items to fail.
Expected Results
Not to create the duplication and synchronise with settings on the server.
Actual Results
2021-03-22 12:28:28.053 ERROR MACS project-import We couldn't import Issue MACS-1. Reason: NullPointerException: There is no step in workflow [Software Simplified Workflow for Project MACS] linked to status [To Do (migrated)]. This caused 4 other items to fail.
Workaround
Not known
