-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
10
-
Severity 3 - Minor
Issue Summary
When migrating projects with JCMA, in theory, the add-on should only migrate the entities related to the selected projects. This also means that only the statuses being referenced in these project workflows should be imported which is not the current behavior.
Right now, when a project is migrated via JCMA all instance statuses are migrated to the Cloud site.
Steps to Reproduce
- Create a sample project.
- Create extra statuses and make sure they are not related to the project's workflow.
- Migrate the project with JCMA.
Expected Results
JCMA should only migrate the statuses related to the workflow from the project being migrated.
Actual Results
JCMA migrates all server statuses into the Cloud.
Workaround
Delete the unwanted statuses after the migration has been finished.
- is related to
-
MIG-254 All issue types migrated every time a migration is run
- Closed
-
MIG-266 All standard and custom fields are migrated every time a migration is run
- Closed
- is implemented by
-
MTOOLS-56 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...