-
Suggestion
-
Resolution: Unresolved
-
None
Description
When migration a condition with "User Is In Group Custom Field", the field ID does not get translated on Cloud.
For eg:
- On DC, the WF Condition is associated to a group picker CF (Customfield_testGroup ID 10001).
- After migration to Cloud, the WF Condition descriptor does not change.
<arg name="class.name">com.atlassian.jira.workflow.condition.InGroupCFCondition</arg> <arg name="groupcf">customfield_10001</arg> - However, on Cloud, the CF ID is most likely to change, new ID 12001. This breaks the reference.
Per https://support.atlassian.com/migration/kb/workflow-rules-migrated-via-jira-cloud-migration-assistant/, it states that "User is in group" is supported. This is a different condition to "User Is In Group Custom Field".
Suggestion
Support migration of "User Is In Group Custom Field" Condition, specifically, translate the CF IDs after migration.
Workaround
Reach out to support for assistance.
- Support could help identify scope of problem (eg: which workflows are affected). Customers can also self serve this by running below query against DB.
select * from jiraworkflows where descriptor like '%com.atlassian.jira.workflow.condition.InGroupCFCondition%'; - Depending on severity of problem, either do manual reconfiguration bulk update on Cloud.
- For bulk update on Cloud, only Atlassian Support can do this.
- Guide for support, we are looking to bulk replace using regex. CF mapping can be retrieved from internal tooling (MAUI).
- For bulk update on Cloud, only Atlassian Support can do this.