Migrate from on-premise (Data Center) to Atlassian Cloud
Background information
Since major release 4.x, this app offers a new custom field type “Group Sign-Off / Multi-Approval Field“, similar to Jira Data Center.
Any custom field of this type can be used in classic company-managed projects as well as in team-managed projects. As an admin, you can create centralized fields in the Jira administration → work items → fields. For team-managed projects, click on the tab “Multi-Approvals” in the section “Activities”. There, you can create/edit/delete such fields if you have project administration permissions.
In team-managed projects, you can directly configure who has to decide, optionally limited by conditions, rules for final sign-off or decline, additional options, etc. All this can be done interactively using the new user interface.
For company-managed projects and related fields, switch to Jira administration → work items → fields → search for your new created field -> expand the context menu on the right side (“…”) -> click on “Context and default values“ → click on “Edit custom field config“: configure interactively who has to decide, etc. similar to the team-managed field(s).
Besides a new and more intuitive admin user interface, additional features are available, for example, the definition of time-outs like (due date - 2w), or advanced searching via JQL.
On the main tab “Advanced”, you can enter a dynamic or static rule, similar to Jira Data Center or the older approach of Jira Cloud (cloud app version 2.x).
Steps to migrate to the Cloud
Please ensure you have upgraded to the latest version of the App in your Jira Data Center (at least 2.10.17 or newer for Jira 10)
Export group sign-off data from Jira Data Center:
Open the system administration menu on the right top of Jira DC as an admin, and click on “Manage Apps”, expand the section “Group Sign-Off/Multi-Approvals for Jira”, and click on “Configure”. There, click on “Export” to generate and automatically download a JSON file of your group sign-off field configurations and all related issues' data.Migrate all your necessary projects, issues, users, project roles, and user groups, etc.
After having already migrated all your other data from Jira Data Center into Jira Cloud, you can import your exported JSON into Jira Cloud:
As an admin, open the menu “Jira admin settings“ on the top right of Jira Cloud, and click on “Marketplace Apps”. There, click on “Group Sign-Off/Multi-Approval for Jira”: now, click on “Import” and select your previously exported JSON file.After successfully uploading your data to Jira Cloud, this data will be processed in the background. Please wait several minutes and/or check your logs to monitor the progress of these activities and identify any problems.
All exported group sign-off fields of Jira Data Center will be created in your Jira Cloud instance. As much as possible, screens and schemes are updated to display these fields; however, not all configurable aspects can be taken into account. That’s why you should check this as an admin in the next step.
All issues' group sign-off fields having a static definition including already happened decisions, will be migrated and transferred from Jira Data Center to Jira Cloud by referencing the issue keys.
Having conditional definitions, a decision has not been started due to non-matching conditions or no decider has been voted up to now. In such cases, no data will be set into group sign-off fields of issues: you must define such conditional rule within the related context of the new created group sign-off field in Jira Cloud as an admin. This is centrally managed in Jira Cloud per context of a group sign-off field, which differs from Jira Data Center.Switch to your Jira Cloud fields and check that the created fields of the new field type “Group Sign-Off/Multi-Approval Field” are available on your required screens, as well as schemes like the “default field scheme”. As there can be a lot of different scenarios and configurations per customer, this cannot be fully automated: it has to be adjusted by an administrator, once.
Once, configure your new group sign-off fields interactively by setting their default behavior, because in Jira Data Center, you would have configured may be a workflow post function to set a group sign-off field’s configuration, or define such a field’s default value, or use any other approach to set a definition in time depending on certain scenarios.
In Jira Cloud, you can more easily configure this by using the “conditional mode” of multiple subsets of deciders as well as a condition for each subset determining when the related subset shall be used.
Also, you can copy & paste your Jira Data Center definitions into the “Advanced config” tab to re-use that code. Due to GDPR, you must adjust such code to avoid referencing user names: instead, use the related accountIDs. Also, refer fields by “issue.fields.xyz” instead of “issue.xyz”.
Sample:
Jira Data Center// conditional rule if (issue.assignee) { users = ""+helper.getUsersByCustomfield(issue, "Approvers", ",") rule = ""+helper.getUsersByCustomfield(issue, "Approvers", "AND"); } else { users = issue.assignee.name + "/* Assignee */, " +helper.getUsersByCustomfield(issue, "Approvers", ",") rule = issue.assignee.name + "/* Assignee */ AND "+helper.getUsersByCustomfield(issue, "Approvers", "AND"); }
Jira Cloud// conditional rule if (issue.fields.assignee) { users = ""+helper.getUsersByCustomfield(issue, "Approvers", ",") rule = ""+helper.getUsersByCustomfield(issue, "Approvers", "AND"); } else { users = issue.fields.assignee.accountId + "/* Assignee */, " +helper.getUsersByCustomfield(issue, "Approvers", ",") rule = issue.fields.assignee.accountId + "/* Assignee */ AND "+helper.getUsersByCustomfield(issue, "Approvers", "AND"); }Finally, switch to the app’s main “configure” page in Jira Cloud …
… and enable the checkbox for “Do not show the older Group Sign-Off panel, instead use custom fields of type "Group Sign-Off/Multi-Approval Field".“ to avoid irritations by users seeing the older fields.
In case of any question, please do not hesitate to contact me at frank@polscheit.de.