Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    MIG-217Support the export/import of the workflow UI positioning in a Jira Server to Cloud migration
  2. Suggestion
    MIG-1044Migrate filter subscriptions
  3. Suggestion
    MIG-2289Insights with recommendations is not available in Portfolio Insights
  4. Suggestion
    MIG-1761JCMA - Better predict board location after migration
  5. Suggestion
    MIG-958JCMA is creating duplicate permission schemes
  6. Suggestion
    MIG-304Dashboard gadgets created by apps do not work post migration
  7. Suggestion
    MIG-547Expose migration mappings on CMAs after a migration
  8. Suggestion
    MIG-568Migration Assistant should allow app only data migrations
  9. Suggestion
    MIG-726Provide total migration time for a JCMA plan
  10. Suggestion
    MIG-1071Diagnostics report for Jira post migration
  11. Suggestion
    MIG-1163Better handling of duplicate fields for migrated sites (server to cloud)
  12. Suggestion
    MIG-1265JQL board filter using filter id doesn’t bring expected results after migrating via JCMA
  13. Suggestion
    MIG-1271Allow migration of users with CCMA without groups
  14. Suggestion
    MIG-1338Support for forward proxy on Application Tunnels
  15. Suggestion
    MIG-1661JCMA - Provide time taken for a migration plan
  16. Suggestion
    MIG-1696Support the migration of Team user defined custom field data
  17. Suggestion
    MIG-1781Issues while migrating and deleting spaces at same time
  18. Suggestion
    MIG-1987Provide an option to migrate pull request history commits using Bitbucket Cloud Migration Assistant (BCMA)
  19. Suggestion
    MIG-2041Scaling of multithreading for increased performance when migrating Confluence attachments using CCMA
  20. Suggestion
    MIG-2124Tool to handle duplicated entities post migration
  21. Suggestion
    MIG-2150JCMA - Dashboards shared with group are not migrated to Cloud
  22. Suggestion
    MIG-2224JCMA to retain filter id inside other JQL filters after migration to cloud
  23. Suggestion
    MIG-2288Sandbox select copy can fail if JSM is not added to sandbox
  24. Suggestion
    MIG-2040"Mentioned on" Confluence page is not displaying on individual Jira issues
  25. Suggestion
    MIG-186Give users the option to remove the migrated text from fields
  26. Suggestion
    MIG-507Provide the corresponding URL information between Confluence Server and Confluence Cloud after migration
  27. Suggestion
    MIG-762JCMA should retain Favorites on Filters that are migrated
  28. Suggestion
    MIG-1084JCMA should provide report on entities that will be duplicated with migration
  29. Suggestion
    MIG-1261Support for linking more than one Atlassian Cloud organisation through Application Tunnels
  30. Suggestion
    MIG-1358JCMA Pre-flight checks should show the entities impacted by 32767 limit
  31. Suggestion
    MIG-1394JCMA should retain Favorites on Dashboards that are migrated
  32. Suggestion
    MIG-1395CCMA - Include the execution time on Migration Plan UI
  33. Suggestion
    MIG-1477Consider migrating project shortcuts when using the Jira Cloud Migration Assistant
  34. Suggestion
    MIG-1487Link fixing should support Space Import migration
  35. Suggestion
    MIG-1589JCMA should include workflow properties in migration
  36. Suggestion
    MIG-1626Link Fixing doesn't fix Confluence links with additional characters in the link
  37. Suggestion
    MIG-1821Configuration only migration for Jira - server to cloud, JCMA
  38. Suggestion
    MIG-1911Provide the Agile board ( Kanban or Scrum) details linked to Business project
  39. Suggestion
    MIG-1967Link Fixing Solution Should support link-updates on existing product in Cloud Site
  40. Suggestion
    MIG-2171CCMA Preflights: CCMA Pre-flight check for "Missing Attachment" takes a long time to complete
  41. Suggestion
    MIG-2189Migrate branch restrictions patterns from DC ending with a "/" as a "/*" to Cloud
  42. Suggestion
    MIG-315Create an API to convert user references stored in JQL to AAID during the migration
  43. Suggestion
    MIG-1021Provide API to convert all JQL from Server to Cloud
  44. Suggestion
    MIG-1208Add ability for Confluence Cloud Migration Assistant to migrate attachments after space migration
  45. Suggestion
    MIG-1519Link fixing following site renames
  46. Suggestion
    MIG-1656CMAs should provide better checks for network problems
  47. Suggestion
    MIG-1658Link fixing should update Bitbucket URLs in Jira after migration of Bitbucket and Jira to Cloud
  48. Suggestion
    MIG-1659Link fixing should update Bitbucket URLs in Confluence after migration of Bitbucket and Confluence to Cloud
  49. Suggestion
    MIG-2018Provide a mechanism to fix product links in server for a hybrid environment
  50. Suggestion
    MIG-2281The link Fixing page fails to load for big migrations
Refresh results
1 2 3 4 5Next >>
1 of 707
Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-217

Support the export/import of the workflow UI positioning in a Jira Server to Cloud migration

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Jira - Migration Assistant - Export
    • None
    • 1,099
    • 100
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

      1. Create a workflow
      2. Position the statuses and transitions on a set layout
      3. Associate this workflow with a workflow scheme
      4. Associate the workflow scheme with a project
      5. 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

        is duplicated by

        Suggestion - MIG-1086 Workflow status(diagram) placement to be carried over during migration.

        • Closed
        mentioned in

        Page Failed to load

        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...

        (9 mentioned in)

            Form Name

              • All
              • Comments
              • Work Log
              • History
              • Activity

              Raghu Gowda added a comment - 11/Apr/2025 9:55 AM

              We were moving all our Data Center projects to Cloud, But Workflow UI is misalignment, as we are in the process of migration 200+ Jira projects to different cloud sites. This is taking lot of time to do those changes in cloud environment. Also, this bug was created in 2020, till now it's not able to fix from Atlassian and this Bug is not assigned.

              Raghu Gowda added a comment - 11/Apr/2025 9:55 AM We were moving all our Data Center projects to Cloud, But Workflow UI is misalignment, as we are in the process of migration 200+ Jira projects to different cloud sites. This is taking lot of time to do those changes in cloud environment. Also, this bug was created in 2020, till now it's not able to fix from Atlassian and this Bug is not assigned.

              George G added a comment - 18/Jul/2024 7:14 AM

              Yeah not surprised this doesn't work... Doubt they will ever fix it either

              George G added a comment - 18/Jul/2024 7:14 AM Yeah not surprised this doesn't work... Doubt they will ever fix it either

              Sami Ahmed Shaik added a comment - 08/Jul/2023 4:50 PM

              This is a must-have feature for JCMA. The migrated workflow UI badly impacts us.

              Sami Ahmed Shaik added a comment - 08/Jul/2023 4:50 PM This is a must-have feature for JCMA. The migrated workflow UI badly impacts us.

              Ashvini Shukla added a comment - 22/Jun/2023 9:53 AM

              https://getsupport.atlassian.com/browse/MOVE-130653

               

              Ashvini Shukla added a comment - 22/Jun/2023 9:53 AM https://getsupport.atlassian.com/browse/MOVE-130653  

              Paddy Byrne added a comment - 10/May/2023 3:44 PM

              +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.

              Paddy Byrne added a comment - 10/May/2023 3:44 PM +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.

              Viktor Sapaiev added a comment - 03/May/2023 1:18 PM

              +1

              Viktor Sapaiev added a comment - 03/May/2023 1:18 PM +1

              Patrizia Kamp - OLD account added a comment - 03/Apr/2023 11:02 AM

              +1

              Patrizia Kamp - OLD account added a comment - 03/Apr/2023 11:02 AM +1

              Javish Kathuria added a comment - 30/Nov/2022 6:23 PM

              Yet another basic feature messing up the view after migration. It's not about changing the UI, atleast persist the old settings

              Javish Kathuria added a comment - 30/Nov/2022 6:23 PM Yet another basic feature messing up the view after migration. It's not about changing the UI, atleast persist the old settings

              Karin van Driel added a comment - 19/Oct/2022 9:42 AM

              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...

              Karin van Driel added a comment - 19/Oct/2022 9:42 AM 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...

              Yevgen Lasman added a comment - 25/Jul/2022 4:12 PM

              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.

              Yevgen Lasman added a comment - 25/Jul/2022 4:12 PM 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.

                Unassigned Unassigned
                dwoo@atlassian.com Daniel Woo
                Votes:
                154 Vote for this issue
                Watchers:
                101 Start watching this issue

                  Created:
                  20/Jul/2020 9:03 PM
                  Updated:
                  1 hour ago
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian