-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
JCMA - 1.12.27
-
None
-
93
-
Minor
-
906
Issue Summary
When migrating from DC2C, the layout of a workflow diagram is lost. Customers will lose the positioning of the statuses and transitions within a workflow, including the drop-down view of an issue transition on the issue view.
Steps to Reproduce
- Create a workflow
- Position the statuses and transitions on a set layout
- Associate this workflow with a workflow scheme
- Associate the workflow scheme with a project
- Migrate the project
Expected Results
The workflow diagram layout is migrated.
Actual Results
The workflow diagram layout is not migrated and all statuses are centerly aligned.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
[MIG-217] Support the export/import of the workflow UI positioning in a Jira Server to Cloud migration
This is a must-have feature for JCMA. The migrated workflow UI badly impacts us.
+1
Also think this is strange that this is not a standard feature. For use-cases outside of the standard software world, it is very common to use Jira to model and track Business Process Flows. These tend to have multiple statuses (20+ not uncommon) and multiple transitions with conditions, validators, and non-linear directions. The current way they get migrated and visualised in could make it impossible to visualise at what stage in the process the issue is really at. It takes many hours to rearrange these (our instance has 40+ complex workflows). As another user posted this cannot be done in a migration weekend, where there are already enough other technical things that need to be done.
Yet another basic feature messing up the view after migration. It's not about changing the UI, atleast persist the old settings
I'm surprised with the number of things that are not supported as standard as part of migration, especially as Atlassian is pushing for people to migrate to cloud so hard... The process should be straight forward and we should not need to do these types of manual workarounds. I guess it is not voted on much as it is only encountered during migration, not day to day usage...
Looks like layout is just not part of the migration, thus Cloud creates is as it can. Hopefully layout will be added soon, otherwise adjusting complex workflows after the migration (which is often required due to unsupported/incompatible conditions, validator and post-functions) is the very painful and time consuming operation.
we just spent 2 MD in total effort for xxx Workflows with xxxx status, this is completely unacceptable, since it is almost impossible to do this within a migration weekend.
I really wonder why there are so few votes
br
Christian
Yeah not surprised this doesn't work... Doubt they will ever fix it either