Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-296

Provide support for all workflow post-functions/validators/conditions/triggers

    • 51
    • 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

      Steps to Reproduce

      1. Migrate a workflow using the Jira Cloud Migration Assistant

      Expected Results

      The workflow and it's scheme including all transitions, statuses, workflow post-functions/conditions/validators/triggers are migrated

      Actual Results

      Only the workflow functions listed on this page are migrated:
      
      https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html

      Workaround

      Manually migrate the workflow functions by editing the workflow in target Jira Cloud site.

            [MIG-296] Provide support for all workflow post-functions/validators/conditions/triggers

            Strange that there should be a suggestion for this: when we migrate it seems to me quite obvious that we want to migrate all the conditions, validations and postfunctions that we had on server. I would treat this as a bug, not a suggestion.

            Gianni Pucciani added a comment - Strange that there should be a suggestion for this: when we migrate it seems to me quite obvious that we want to migrate all the conditions, validations and postfunctions that we had on server. I would treat this as a bug, not a suggestion.

              103579c89d5e Shraddha Garg
              jwong@atlassian.com Jason Wong
              Votes:
              28 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated: