| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
1. Update permissions
After migrating, you will need to review all your permissions schemes.
In default Cloud permission schemes apps are granted all required permissions to project role atlassian-addons-project-access, The Scheduler requires to add this role atlassian-addons-project-access to all permissions otherwise app may not work properly.
(Remember to verify our app permissions Permissions )
...
It is equally important that the administrator adds users to the appropriate groups (Settings → Atlassian Admin → User Management) . These groups are created automatically when the migration is complete, and without assigning users to them, the Scheduled Issues will not execute correctly.
| Info |
|---|
If the Administrator does not assign users to the appropriate groups before executing Scheduled Issues, all SIs with a status of Failed will need to be edited after rights have been granted. It is important to reassign the migrated users, only then will the SIs be active. |
Above the main menu you will see a bar with information about importing groups, click review now (1).
...
You will need to click on review (2) all imported groups one by one and approve (3) them as you wish.
...
Once all groups and product roles have been confirmed, the User Management page will be displayed with a message confirming the successful actions. When the page refreshes, the yellow bar should disappear.
...
You can always check that your choices have been saved by going to the details of a particular user (4) and checking the section Product Access (5).
...
The next step is to add users to migrated groups. You will need to select Add user to group (6) and select the appropriate name of the group (7) to which the user should belong.
...
| Info |
|---|
It is important that the name of the group we choose includes the name of the instance on the Cloud that we have chosen to migrate to. |
...
When you have added the user to all the required groups, click Add Groups button. You will be returned to the screen and a success message will appear in the bottom left corner.
...
In the user profile, the name of the selected group should appear in the Group membership section (8).
...
This should be done for all migrated users - assign them to migrated groups.
| Info |
|---|
Correctly adding users to migrated groups:
|
Below are examples of how the application behaves before and after adding users to groups.
...
2. What can look different
2.1 Mentioned users formatting
When eg. in description of The Scheduled issue you mentioned user:
...
after migration at cloud side it will have different format:
...
2.2 Text formatting
Text decorators like italic, bold, underline or applying color on server side like:
...
after migration to cloud will look:
...
2.3 Scheduled issues states
Due to fact that not everything is migrated, states of the Scheduled Issues will be mapped after migration according to following rules:
Invalid → Disabled
Active → Active
Inactive → Disabled
Skipping → Skipping
Calendar day off → Active
Pending → Active
Expired → Expired
2.4 Scheduled Issues with multiple triggers
Due to the fact that the Cloud version of the app doesn't support multiple triggers, when Scheduled Issue with multiple trigger is migrated from Server / DC, it needs to split. It ensure that all planned executions are covered.
Exemplary Scheduled Issue with multiple triggers in Server:
...
after migration to Cloud it is split:
...
Please note that when trigger is not supported in Cloud (eg. workflow trigger) it will not be migrated as in the example above.