Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8317 Team-managed Jira Service Desk Projects
  3. JSDCLOUD-8953

The "Work on requests" permission under Next-Gen manage roles should contain the product access warning

    • Icon: Sub-task Sub-task
    • Resolution: Won't Fix
    • Icon: Low Low
    • None
    • None
    • None

      Problem

      While creating a new project role on a next-gen project, the permission "Work on requests" does not say that the user must have the application access of Jira Service Desk to have that working.

      Suggested resolution

      Add the product access warning to this permission too.

            [JSDCLOUD-8953] The "Work on requests" permission under Next-Gen manage roles should contain the product access warning

            Matthew Hunter made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels New: timeout-suggestion-bulk-close

            Atlassian Update - September 22, 2022

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - September 22, 2022 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            Paul Kraus added a comment -

            If Service Desk Next Gen role of Work requires Service Desk access (and license), then "Log work on any request" (time tracking) should move to the Collaborate role so that non-Service Desk staff can still work on issues and track time (without directly interacting with the customer). See https://jira.atlassian.com/browse/JSDCLOUD-1240 

            Paul Kraus added a comment - If Service Desk Next Gen role of Work requires Service Desk access (and license), then "Log work on any request" (time tracking) should move to the Collaborate role so that non-Service Desk staff can still work on issues and track time (without directly interacting with the customer). See  https://jira.atlassian.com/browse/JSDCLOUD-1240  
            Eduardo Santos created issue -

              Unassigned Unassigned
              esantos@atlassian.com Eduardo Santos
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: