Existing Workflow Condition in Cloud Didn't Override After Project Migration from DC

[Digvijay Singh Gehlot]

Hi Community,

I have set a Workflow Condition in Cloud and want to override/ replace it with DC Workflow Condition during migrating Project from DC to Cloud via JCMA

For eg: In Could, I have Condition "User Is In Any Users (JSM)" in workflow. In DC, I have condition "User Is In Group" in workflow.

Now I want that after project migration via JCMA, the existing Cloud condition should override/ replace by DC Condition but it is not happening.

Please provide detailed explanation why it is not happening or if it is possible, then how I can achieve this.

Thanks

[Marc - Devoteam · Accepted solution]

Hi @Digvijay Singh Gehlot 

These are different conditions JCMA converts workflows as is, there is not option to have JMCA make changes.

This is a manual action to be done after migration.

[Digvijay Singh Gehlot]

Thank you @Marc - Devoteam for your message.

May you help me with, which Triggers/Conditions/Validations/Post-functions can be migrated from DC to Cloud, if such configurations are already there in Cloud Workflow?

[Marc - Devoteam]

Hi @Digvijay Singh Gehlot 

Only default ootb Triggers/Conditions/Validations/Post-functions can be migrated.

Any Triggers/Conditions/Validations/Post-functions added by marketplace apps will only be migrated if after the app assessment the conclusion is that the app is applicable for migration and a migration app is provided by the vendor.

Specific documentation on workflows and JCMA can be found here: workflow-rules-migrated-via-jira-cloud-migration-assistant