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

    • 81
    • 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

          Form Name

            [JSDSERVER-1256] Restricting 'Delete' permission should NOT count as a permission scheme error

            It boggles the mind how this suggestion was created in 2014 and nothing has been done in 9-10 years. Per their own documentation, as described in one of the attachments, they themselves say to "think carefully about which groups or project roles that you assign this [delete issues] permission to." 

            How can we think carefully about who to assign the Delete Issues permission to if it is forced upon us?

            Brian Preuss added a comment - It boggles the mind how this suggestion was created in 2014 and nothing has been done in 9-10 years. Per their own documentation, as described in one of the attachments, they themselves say to "think carefully about which groups or project roles that you assign this [delete issues] permission to."  How can we think carefully about who to assign the Delete Issues permission to if it is forced upon us?

            How is this not a bug?!

            Richard Lange added a comment - How is this not a bug?!

            I am also in agreement, we do not want to allow any user to delete an issue, and have a set process if this is ever required.  Therefore we have removed even admins from having the ability to delete, so do not wish to see this error message, as when clicking on the show more info, it does not even mention the delete option in the list, so unsure why we see this error message

            Collette Gray added a comment - I am also in agreement, we do not want to allow any user to delete an issue, and have a set process if this is ever required.  Therefore we have removed even admins from having the ability to delete, so do not wish to see this error message, as when clicking on the show more info, it does not even mention the delete option in the list, so unsure why we see this error message

            Leo Chung added a comment -

            In JSM, there are quite a few default permissions assigned to the Portal access users, ie: delete, move.... etc.

            When we remove any of these permissions, the popup error in the Project is misleading. Ideally for our firm, we do not allow anyone to delete issues, especially not portal access users. We need a way to not throw this error every time a project user access the project.

            Leo Chung added a comment - In JSM, there are quite a few default permissions assigned to the Portal access users, ie: delete, move.... etc. When we remove any of these permissions, the popup error in the Project is misleading. Ideally for our firm, we do not allow anyone to delete issues, especially not portal access users. We need a way to not throw this error every time a project user access the project.

            For my team, we do not want anyone to delete issues under any circumstances except as an Admin. This helps us to see how our techs are doing with creating tickets correctly, timely and appropriately.  We also do not want anyone to be able to delete comments.  Again, this forces our techs to ensure that they stay professional and on key in their tickets. 

            Allison Stewart added a comment - For my team, we do not want anyone to delete issues under any circumstances except as an Admin. This helps us to see how our techs are doing with creating tickets correctly, timely and appropriately.  We also do not want anyone to be able to delete comments.  Again, this forces our techs to ensure that they stay professional and on key in their tickets. 

            There are certain processes where it is no good idea to delete at all... I don't get why they should be able to delete... You have plenty of possibilities to close an Issue with an according state/resolution. So it's better to have it documented why it won't be processed than just deleting it and cause misunderstandings and confusion.

            Michael Aglas added a comment - There are certain processes where it is no good idea to delete at all... I don't get why they should be able to delete... You have plenty of possibilities to close an Issue with an according state/resolution. So it's better to have it documented why it won't be processed than just deleting it and cause misunderstandings and confusion.

            Ahhhh, that is a very good question and an excellent point!  I have a couple admins because they need to write reports and since I'm the only TRUE admin, I can't support this entire company and all departments.  So I've allowed them access to modify their workflows and such.  Risky, yes.  But necessary at this time.

            I'll email all of my admins and remind them to DISMISS, not FIX.

            Thank you so much for the insight.

            Allison Stewart added a comment - Ahhhh, that is a very good question and an excellent point!  I have a couple admins because they need to write reports and since I'm the only TRUE admin, I can't support this entire company and all departments.  So I've allowed them access to modify their workflows and such.  Risky, yes.  But necessary at this time. I'll email all of my admins and remind them to DISMISS, not FIX. Thank you so much for the insight.

            Dan W added a comment -

            08287db7dd59,  How many admins do you have?  If any of them click the fix issues button it will revert your change.    

            Dan W added a comment - 08287db7dd59 ,  How many admins do you have?  If any of them click the fix issues button it will revert your change.    

            I am on Cloud and don't see the option to change the Permission Scheme Error message.  Can anyone help?

            But also, it seems that when I remove the Delete Issues permission from my Service Desk Team Members... after a while, the system just reverts the permission BACK to Allow.  I don't even know when or how that happens which means randomly, my Agents can delete issues.  And I don't even know about it!

            Please implement this as soon as humanly possible.

            Allison Stewart added a comment - I am on Cloud and don't see the option to change the Permission Scheme Error message.  Can anyone help? But also, it seems that when I remove the Delete Issues permission from my Service Desk Team Members... after a while, the system just reverts the permission BACK to Allow.  I don't even know when or how that happens which means randomly, my Agents can delete issues.  And I don't even know about it! Please implement this as soon as humanly possible.

            This would be very helpful for our team. We need to keep records of all of our tickets, even if they have been cancelled, and as-such have turned the delete function off. Jean-Francois' work-around unfortunately does not work for our users as we operate multiple service desks and only are team are main administrators. We've had multiple complaints around this from users. The warnings are important and shouldn't be removed, but a 'Disable this Issue' button (ie. stop alerts around that specific issue, but not new errors from popping-up when they occur) would be fantastic. 

            atlassian.support added a comment - This would be very helpful for our team. We need to keep records of all of our tickets, even if they have been cancelled, and as-such have turned the delete function off. Jean-Francois' work-around unfortunately does not work for our users as we operate multiple service desks and only are team are main administrators. We've had multiple complaints around this from users. The warnings are important and shouldn't be removed, but a 'Disable this Issue' button (ie. stop alerts around that specific issue, but not new errors from popping-up when they occur) would be fantastic. 

              Unassigned Unassigned
              6c8e2aa384e8 Oliver
              Votes:
              183 Vote for this issue
              Watchers:
              99 Start watching this issue

                Created:
                Updated: