Gabriel Bucher {Appfire} added a comment - 14/Feb/2022 5:09 AM Thank you Hariharan, we will check and if we find any issue, we will report back.

Hariharan Rajendran (Inactive) added a comment - 11/Feb/2022 1:44 AM Released with JCMA v1.6.7.

Hariharan Rajendran (Inactive) added a comment - 11/Feb/2022 1:43 AM Hi a91b62b45152 , This issue has been resolved with JCMA 1.6.7. We are closing this issue as JCMA 1.6.7 is available in marketplace. Please reach us back, if you are facing any issues in migrating com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition and com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition with JCMA 1.6.7. Regards, Hariharan.

Yevgen Lasman added a comment - 10/Feb/2022 3:48 AM Released in v1.6.7

Callum Bundy added a comment - 20/Jan/2022 4:00 AM Currently working on implementing this, we hope to have an update soon.

Gabriel Bucher added a comment - 19/Jan/2022 10:02 AM Hi Hariharan, thank you for your comment. Regarding your questions: Question 1: YES, this matches our expectation. Question 2: We do not have any details if in a workflow transition on the server side would have both variation configured. I believe the current approach you take in this scenario to treat them separate is a sensible way.  Thanks Gabriel

Hariharan Rajendran (Inactive) added a comment - 11/Jan/2022 4:02 AM - edited Hi a91b62b45152 , We are doing a spike on migrating com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition and com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition workflow transition rules. With our changes for this spike, JCMA will be migrating the user in any project roles and user in any group conditions as follows, Server Condition  Cloud Condition Status com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition com.atlassian.jira.workflow.condition.InAnyProjectRoleCondition Will be supported once this MIG is delivered com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition com.atlassian.jira.workflow.condition.UserInAnyGroupCondition Will be supported once this MIG is delivered com.atlassian.jira.workflow.condition.InProjectRoleCondition com.atlassian.jira.workflow.condition.InAnyProjectRoleCondition Supported since JCMA 1.5.1 com.atlassian.jira.workflow.condition.UserInGroupCondition com.atlassian.jira.workflow.condition.UserInAnyGroupCondition Supported since JCMA 1.5.1 We wish to share the results we got so far with you and confirm whether our results matches your expectation on this, Server condition Migrated cloud condition <condition type="class"> <arg name="hidRolesList">Administrators@@Service Desk Customers@@Service Desk Team@@</arg> <arg name="jsuWorkflowParamsVersion-textValue">2.32.0</arg> <arg name="class.name">com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition</arg> <arg name="uuid">af5e0100-34e4-4184-9017-6da5786075cb</arg> </condition> <condition type="class"> <arg name="class.name">com.atlassian.jira.workflow.condition.InAnyProjectRoleCondition</arg> <arg name="projectRoleIds">10004@@10010@@10011@@</arg> </condition> Where the projectRoleIds 10004, 10010, 10011 are the references to the project roles migrated to the cloud. <condition type="class"> <arg name="jsuWorkflowParamsVersion-textValue">2.32.0</arg> <arg name="class.name">com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition</arg> <arg name="uuid">8fe7e531-ad55-470e-8fe3-50d6988ded8f</arg> <arg name="hidGroupsList">jira-administrators@@jira-servicedesk-users@@jira-software-users@@</arg> </condition> <condition type="class"> <arg name="class.name">com.atlassian.jira.workflow.condition.UserInAnyGroupCondition</arg> <arg name="group">jira-administrators@@jira-servicedesk-users@@jira-software-users@@</arg> </condition> <condition type="class"> <arg name="jira.projectrole.id">10002</arg> <arg name="class.name">com.atlassian.jira.workflow.condition.InProjectRoleCondition</arg> </condition> <condition type="class"> <arg name="class.name">com.atlassian.jira.workflow.condition.InAnyProjectRoleCondition</arg> <arg name="projectRoleIds">10004</arg> </condition> <condition type="class"> <arg name="class.name">com.atlassian.jira.workflow.condition.UserInGroupCondition</arg> <arg name="group">jira-administrators</arg> </condition> <condition type="class"> <arg name="class.name">com.atlassian.jira.workflow.condition.UserInAnyGroupCondition</arg> <arg name="group">jira-administrators</arg> </condition>   Please refer to the following snapshots to know how com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition and com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition conditions appeared on server UI and  on cloud UI after migration. Server UI   Cloud UI Question 1 : Does the above results matches your expectations for this MIG ticket ? Question 2 : Do you see any cases where a specific workflow transition on server side can have, both com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition and com.atlassian.jira.workflow.condition.InProjectRoleCondition with same configurations both com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition and com.atlassian.jira.workflow.condition.UserInGroupCondition with same configurations In case of such scenarios, the current solution we are spiking will treat them as separate conditions and migrate those conditions separately (no deduplications will be performed during the migration). Thanks, Hariharan.    

Gabriel Bucher {Appfire} added a comment - 21/Sep/2021 2:57 AM - edited Hi Hedieh & Jax thank you for look into this issue. Atlassian integrated years ago some Condition/Validator/Post-Function from JSU directly into Jira Cloud as native Condition/Validator/Post-Function. JSU does not provide them on our cloud offering today!  At the current stage, JCMA is migrating the following JSU Server Workflow Items to their Jira Cloud native counterparts. "com.googlecode.jsu.workflow.condition.UserIsInCustomFieldCondition" "com.googlecode.jsu.workflow.condition.ValueFieldCondition" "com.googlecode.jsu.workflow.validator.DateCompareValidator" "com.googlecode.jsu.workflow.validator.DateExpressionCompareValidator" "com.googlecode.jsu.workflow.validator.FieldsRequiredValidator" "com.googlecode.jsu.workflow.validator.RegexpFieldValidator" "com.googlecode.jsu.workflow.validator.WindowsDateValidator" for us unknown reasons the following 2 JSU Conditions which also exists in Jira Cloud as native Conditions, are not implemented in JCMA to be migrated! "com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition" "com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition" this issue is to request that JCMA is also migrating the 2 above Conditions to the native counterpart: "com.googlecode.jsu.workflow.condition.UserIsInAnyGroupsCondition" => "com.atlassian.jira.workflow.condition.UserInAnyGroupCondition" "com.googlecode.jsu.workflow.condition.UserIsInAnyRolesCondition" => "com.atlassian.jira.workflow.condition.InAnyProjectRoleCondition" We created years ago a guide for customers who like to migrate from Jira Cloud to Jira Server/DC. https://beecom-products.atlassian.net/wiki/spaces/JSU/pages/25680514/Migrating+from+Jira+Cloud+to+Jira+Server   You can find in the bottom half xml snippets which compare the JSU Condition to the native counterpart.  

Hedieh Jamshidian added a comment - 21/Sep/2021 1:11 AM Hi   a91b62b45152  and fba580d84cf0 , In order to investigate the situation further, we would need some extra details. Could you please provide us: 1) XML export of the workflow in the server 2) XML export of the workflow in the cloud 3) Screenshot of the workflow conditions page in the server 4) Screenshot of the workflow conditions page in the cloud   Cheers, Hedieh Jamshidian Software Engineer, Atlassian Cloud Migrations

Jax Gibb (Inactive) added a comment - 20/Sep/2021 5:28 AM - edited The work mentioned above (in JCMA 1.5.1) covers the following: com.atlassian.jira.workflow.condition.UserInGroupCondition com.atlassian.jira.workflow.condition.InProjectRoleCondition These are the conditions generated through the UI now.