Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-3744

Restricting agents from viewing reports on JIRA Service Desk projects.

    • 1
    • 7
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Customer wants to restrict access of his agents to reports on JIRA Service Desk projects by setting different permissions to certain reports.

      Update - 28th September 2022

      We appreciate the merit of this issue. As JSM is expanding to non-IT teams, we recognise the need for non-IT teams to have autonomy and privacy in managing their projects and tickets. We aim to resolve this strategically as part of the long-term roadmap. However, at the moment we will not be able to share a concrete timeline. 

      Thanks,

      JSM Team.

            [JSDCLOUD-3744] Restricting agents from viewing reports on JIRA Service Desk projects.

            Hello all

             

            According to new Data Protection Laws and as well as the Usage of Atlassian AI being promoted, I think there should be put more emphasis on the restriction of Data View Access for certain User Groups. 

             

            Following Example:
            Imagine you use JSM and your Agent gets a very Bad Satisfaction Rating on his ticket and a bad comment. There is no option to delete the comment and satisfaction rating, other than deleting the whole Ticket or creating a Ticket with Atlassian for deleting the satisfaction record. And then somebody who is agent and maybe in a leading position uses Atlassian AI to get a summary of all Agents who have received a one star rating or a bad comment on his Ticket. 

            Is there any workaround, or possibility other than straight away deleting records from JSM to prevent abuse of such data?

             

            Kind regards, 
            Severin

            Severin Sutter added a comment - Hello all   According to new Data Protection Laws and as well as the Usage of Atlassian AI being promoted, I think there should be put more emphasis on the restriction of Data View Access for certain User Groups.    Following Example: Imagine you use JSM and your Agent gets a very Bad Satisfaction Rating on his ticket and a bad comment. There is no option to delete the comment and satisfaction rating, other than deleting the whole Ticket or creating a Ticket with Atlassian for deleting the satisfaction record. And then somebody who is agent and maybe in a leading position uses Atlassian AI to get a summary of all Agents who have received a one star rating or a bad comment on his Ticket.  Is there any workaround, or possibility other than straight away deleting records from JSM to prevent abuse of such data?   Kind regards,  Severin

            Hi,

            There has not been any update in more than a year. This feature is really important, IT or not, we should be able to restrict access to reports for agents.

            Can we have an updated timeline please.

            Thanks

            Fanny Vachet added a comment - Hi, There has not been any update in more than a year. This feature is really important, IT or not, we should be able to restrict access to reports for agents. Can we have an updated timeline please. Thanks

            As JSM is expanding to non-IT teams, we recognise the need for non-IT teams to have autonomy and privacy in managing their projects and tickets. We aim to resolve this strategically as part of the long-term roadmap. However, at the moment we will not be able to share a concrete timeline. 

            Yuval Refaeli (Inactive) added a comment - As JSM is expanding to non-IT teams, we recognise the need for non-IT teams to have autonomy and privacy in managing their projects and tickets. We aim to resolve this strategically as part of the long-term roadmap. However, at the moment we will not be able to share a concrete timeline. 

            Note: ticket description was updated with a new status

            Yuval Refaeli (Inactive) added a comment - Note: ticket description was updated with a new status

            Please take this into reconsideration as announced in your note from Nov 2020. 

            Thanks

            Beatrice Glienke added a comment - Please take this into reconsideration as announced in your note from Nov 2020.  Thanks

            As others have stated above, reporting exposes sensitive information about workloads, performance, metrics, etc and may not be suitable for all users to access. 

            The ability to restrict reporting is vital to many scaled and non-scaled organizations, and something I would expect to see as a permission configuration. 

            Meg Holbrook added a comment - As others have stated above, reporting exposes sensitive information about workloads, performance, metrics, etc and may not be suitable for all users to access.  The ability to restrict reporting is vital to many scaled and non-scaled organizations, and something I would expect to see as a permission configuration. 

            This essentially allows any agent to view performance metrics / satisfaction for any other employee. Human Resources won't allow this, and may actually be against the law. Without being able to restrict this, this will kill our Jira project. I noticed this request is over 3 years old however, so I'm not hopeful this is being addressed.  

            Scott Anderson added a comment - This essentially allows any agent to view performance metrics / satisfaction for any other employee. Human Resources won't allow this, and may actually be against the law. Without being able to restrict this, this will kill our Jira project. I noticed this request is over 3 years old however, so I'm not hopeful this is being addressed.  

            ADMCAZ added a comment -

            I also would like this feature to go forward. We are at an early stage of Service Desk and might not even implement performance tracking as designed by the reports, thus giving the wrong impression to our employees. Please, consider this feature to be released.

            ADMCAZ added a comment - I also would like this feature to go forward. We are at an early stage of Service Desk and might not even implement performance tracking as designed by the reports, thus giving the wrong impression to our employees. Please, consider this feature to be released.

            Please add new permissions called reporting only for senior management to be able to generate reports only while we would like to restrict them from browsing projects.

            Currently we won't be able to restrict access from a user to only be able to see the reports in JIRA Service Desk, as JIRA considers that the reports are part of the "Browse projects" permission and "Service Desk Team" role

            MAGED Youssef added a comment - Please add new permissions called reporting only for senior management to be able to generate reports only while we would like to restrict them from browsing projects. Currently we won't be able to restrict access from a user to only be able to see the reports in JIRA Service Desk, as JIRA considers that the reports are part of the "Browse projects" permission and "Service Desk Team" role

            For our Project Managers we'd like to provide them access to the reports, but it's essential they don't have access to the queues.

            Please provide a solution asap.

            David Anema added a comment - For our Project Managers we'd like to provide them access to the reports, but it's essential they don't have access to the queues. Please provide a solution asap.

              Unassigned Unassigned
              epereira@atlassian.com bpevandro (Inactive)
              Votes:
              28 Vote for this issue
              Watchers:
              32 Start watching this issue

                Created:
                Updated: