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

Restricting 'Delete' permission should NOT count as a permission scheme error

XMLWordPrintable

    • 28
    • 18
    • 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.

      NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Current Behavior

      In a Jira Service Management project, the "Delete Issues" permission includes the following:

      • Project Role (Administrators)
      • Project Role (Service Desk Team)
      • Service Desk Customer - Portal Access

      Removing these permissions causes Jira Service Management to present an error saying there is a problem with the permission scheme that needs to be corrected.

      Suggested Change

      Make it so that changes to the "Delete Issues" permission do not cause a Jira Service Management permission scheme error.

      Example Use Case

      As an administrator, I don't want agents being able to delete tickets - it creates a hole in the ticket ID sequence and if that ticket/request has involved multiple agents then it's very confusing.

      I have changed the default permission scheme so that only administrators can delete issues, but now I'm getting a 'Permission scheme error'.

      I'm choosing to ignore it, but I'd MUCH prefer if it wasn't there

        1. image-2017-09-27-13-08-04-340.png
          image-2017-09-27-13-08-04-340.png
          206 kB
        2. image-2017-09-27-13-11-18-875.png
          image-2017-09-27-13-11-18-875.png
          133 kB

              Unassigned Unassigned
              6c8e2aa384e8 Oliver
              Votes:
              180 Vote for this issue
              Watchers:
              97 Start watching this issue

                Created:
                Updated: