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

The ability to remove 'Project Role (Service Desk Team)' from 'Service Desk Agent' project permission

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • 1
    • 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.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Summary

      When removing the 'Project Role (Service Desk Team)' role from the 'Service Desk Agent' project permission, JIRA Service Desk indicates there is an issue with the Permission scheme.

      Environment

      JIRA Service Desk 3.2.6.

      Steps to Reproduce

      1. Create a Service Desk project or open an existing Service Desk project.
      2. Remove the 'Project Role (Service Desk Team)' project role from the 'Service Desk Agent' permission.
      3. Load the Service Desk project.

      Expected Results

      Users should be able to access the Service Desk without issue.

      Actual Results

      A modal popup is displayed indicating there is an issue with the Service Desk projects Permission Scheme and offers to resolve the issue.

      Notes

      The following popup can be seen:

      Workaround

      The current workaround is to leave this group within the project role.

        1. permission_error.png
          permission_error.png
          34 kB

          Form Name

            [JSDSERVER-4582] The ability to remove 'Project Role (Service Desk Team)' from 'Service Desk Agent' project permission

            Charlie Marriott added a comment -
            Atlassian Update – 1 Feb 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 1 Feb 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

              Unassigned Unassigned
              mmuthusamy Moga
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: