Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-334

Improve the migrate permission scheme process

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    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
      • Administrator
      • Helpdesk
      • Helpdesk & Second Level
      • Second Level
      • Users
      • Administrator
      • Helpdesk
      • Helpdesk & Second Level
      • Second Level
      • Service Desk Team
      • Service Desk Customer
      • Users

      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

          Activity

            People

              Unassigned Unassigned
              4e81381d415c Tim Eddelbüttel
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync