Details
-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
1
-
Description
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Actual
When you choose Migrate permission scheme then it only changes the scheme and nothing more.
Description
If you have an existing project with enabled comment security by project roles these will not change.
Roles before Migration | Roles after Migration |
---|---|
|
|
The team will now see 2 additional roles.
When you remove the users from the not needed roles (e.g. Helpdesk & Second Level becomes Service Desk Team) they will not see their old comments.
To fix this you have to manipulate the database.
Expected
Create an interactive migration process where you choose your existing roles and which it should be. Then all existing issue comments will changed automatically.
Due to the greater impact of this change (see additional), restrict the migration only to users with jira-administrators permission.
Additional
Extend the migration notes that an adminstrator has more to change than the permission scheme if:
- you have a notification scheme with roles
- you have groovy or jelly scripts which contains the old role name or role id
- you have an issue security level which contains these roles
- you have to role based conditions / validators / post functions in your workflow
Attachments
Issue Links
- is related to
-
JSDSERVER-905 Project administrator is able to migrate Permission Scheme
- Closed
-
JSDSERVER-1721 Allow admins to customise JIRA Service Desk permission schemes
- Closed
- relates to
-
JSDCLOUD-334 Improve the migrate permission scheme process
- Closed