Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Current »

The Post Migration page provides a way for you to view and address any issues that were encountered during the migration of workflows using JMWE post-functions/conditions/validators from Jira Server/Data Center to Jira Cloud using the Jira Cloud Migration Assistant (JCMA). These errors and warnings must be addressed in order for your transitions to function.

The Post migration page is only visible on instances where JMWE has been migrated from Jira Server/Data Center to Jira Cloud using the JCMA.

Please note:

  • Currently, Shared actions, Event-based actions, and Scheduled actions are not migrated. You must recreate these manually on your Cloud instance.

  • Any JMWE conditions, validators, and/or post-functions where you employed Groovy scripting will throw errors and will need to be updated with either Jira expressions or Nunjucks expressions/scripts.

  • Because Jira Cloud runs post-functions after a transition completes, there are no error handling capabilities in Jira Cloud to prevent transitions from completing. Post-functions that include error handling in your Server/DC instance will display warnings on the Post migration page.

  • The Return to Previous Status post-function is not migrated from Server as there is no equivalent on the Cloud version. JCMA will report this in the logs on the server side during migration.

Shared actions, Event-based actions, and Scheduled actions

Currently, Shared actions, Event-based actions, and Scheduled actions are not migrated and must be manually recreated for use in Jira Cloud. If you have any of these actions in your Jira Server/Data Center instance, a warning box displays with links that direct you back to those actions in your Jira Server/Data Center instance for easy reference.

You can Dismiss this message when you have recreated these actions and events.

Viewing errors and warnings to workflows

Select a Workflow to view the errors and warnings that must be addressed.

Only migrated workflows that contain errors and/or warnings are displayed in the Workflow dropdown menu.

Once you have selected your workflow, you can group by:

  • Transition, which shows details of all the workflow extensions associated with each affected transition, or

  • Extension type, which shows details of each type of affected workflow extensions, that is Post function, Condition, Validator.

The list of errors and warnings displays. Each shows descriptive text as to the reason the error/warning occurred and suggestions on how to fix the problem.

Addressing errors and warnings

To manually address each error:

  1. Click the Edit button next to the error.

  2. The configuration for the extension that requires your attention appears on top of the Post Migration page with information on where edits are required.

  3. A list of items that need to be addressed appears at the top. After editing, if you have resolved all issues on the extension, click the Save and resolve all problems button. When you return to the Post Migration page, the error will no longer appear. (This may require you to refresh the page.)
    For each item in the list you can also Mark as resolved, or Mark all as resolved, to cross these items off the list. Otherwise, click the Save button and you can return to this page later to finish your edits.

  4. When all errors for a workflow have been addressed, the workflow no longer appears in the Workflow dropdown. (This may require you to refresh the page.)

Repeat these steps for all workflows that display in the Workflow dropdown.

  • No labels