• 1,317
    • 163
    • 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 Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 04 November 2024

      Hi everyone,

      Thank you for taking the time to share your challenges around identifying where groups are utilised within Jira. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the next 12-18 months. We will be maintaining this ticket's status as "Gathering Interest" in order to continue learning from all of you about pain points and challenges relating to this suggestion, and will continue to re-visit this ticket in our ongoing product planning.

      We understand that this is not the update you may have been hoping for, especially given the longstanding nature of this issue. Please don't hesitate to contact me if you have any questions or feedback.

      Regards,
      Aditi Dalal
      adalal@atlassian.com
      Product Manager, Jira Cloud

      Currently we only show when a group is used in:

      • Permission Schemes
      • Notification Schemes
      • Issue Security Schemes
      • Shared filters

      A more complete list of locations where a group can be used is:

      • Permission Schemes
      • Notification Schemes
      • Issue Security Schemes
      • Shared filters
      • Project Roles
      • Global Permissions
      • Custom field values
      • Post functions in workflows
      • Conditions in workflows
      • Shared dashboards
      • Filter subscriptions
      • Plugins (we can't help check this one, because we don't know how plugins will use this)

      We should extend this functionality to check as many places as possible because understanding the impact of changes to groups is very difficult for admins at this time.

      Workaround

      Permissions schemes
      https://confluence.atlassian.com/jirakb/how-to-find-group-usage-in-permission-schemes-for-jira-cloud-via-rest-api-and-python-1217306462.html

      Filters
      A user with the Administer Jira Global permission can go to 
      YOUR_SITE_NAME.atlassian.net/rest/api/3/filter/search?expand=jql&overrideSharePermissions=true

      and search for the group name to see which filter it is used in.

      Once you know the filter's name you can go to
      YOUR_SITE_NAME.atlassian.net/secure/admin/filters/ViewSharedFilters.jspa and make yourself its owner or delete the filter:

        1. groupUsage.txt
          3 kB
        2. screenshot-1.png
          screenshot-1.png
          278 kB

            [JRACLOUD-36740] Extend Group administration page to show more use locations

            Dear Atlassian team,

            I kindly ask you to take this issue under consideration again. You have built a powerful, but also complex environment, in which managing of groups is a central aspect to create and keep control over rights, permissions and license usage across a multitude of products, projects, spaces and so on. In order to manage this, it is necessary to be able to manage groups, so creation, reordering, renaming and deletion of groups. Right now, deleting the wrong group can render whole spaces in Confluence unusable. (Page restriction on landing page of a confluence space set to that group, deletion of group leads to "ghost restriction" that cannot be removed by user or admin and hides the complete space with all pages from any kind of access, only solveable by cotnacting Support.)

             

            Unless you identify and solve any issue regarding these permission management topics - which I assume isn't easy - giving your users and admins the option to at least see each and every usage of a user group is essential.

            Regards

            Michel Kangro

            Michel Kangro added a comment - Dear Atlassian team, I kindly ask you to take this issue under consideration again. You have built a powerful, but also complex environment, in which managing of groups is a central aspect to create and keep control over rights, permissions and license usage across a multitude of products, projects, spaces and so on. In order to manage this, it is necessary to be able to manage groups, so creation, reordering, renaming and deletion of groups. Right now, deleting the wrong group can render whole spaces in Confluence unusable. (Page restriction on landing page of a confluence space set to that group, deletion of group leads to "ghost restriction" that cannot be removed by user or admin and hides the complete space with all pages from any kind of access, only solveable by cotnacting Support.)   Unless you identify and solve any issue regarding these permission management topics - which I assume isn't easy - giving your users and admins the option to at least see each and every usage of a user group is essential. Regards Michel Kangro

            Dear Atlassian Team,

            with regards to group usage for the Cloud environment:

            please consider at least to implement the group usage as it is in Jira Server/DC. I am referring to this setting: 

            This still lacks the option to see, where a group has project roles but would definitely be a good first step to make it a bit easier for customers to identify group usage in the Cloud. 

            In Jira Cloud the only way for customers to currently identify group usage to some extend is through the REST API, as SQL is not an option in the Cloud. Or Atlassian Support is kind enough to execute the SQL Statements...

            But in my opinion utilizing the REST API ( through curl or a Python Script) shouldn't be the first step for customers/admins that they need to rely on. It would be better if there would be at least some fundamental reporting features through the GUI for group usage. (perhaps in Atlassian Administration > groups > open a group > three dots > show group usage). 

            Kind regards,

            Christian Winter 

            Christian Winter added a comment - Dear Atlassian Team, with regards to group usage for the Cloud environment: please consider at least to implement the group usage as it is in Jira Server/DC. I am referring to this setting:  see picture under purpose heading:  https://confluence.atlassian.com/jirakb/how-to-identify-group-usage-in-jira-441221524.html This still lacks the option to see, where a group has project roles but would definitely be a good first step to make it a bit easier for customers to identify group usage in the Cloud.  In Jira Cloud the only way for customers to currently identify group usage to some extend is through the REST API, as SQL is not an option in the Cloud. Or Atlassian Support is kind enough to execute the SQL Statements... But in my opinion utilizing the REST API ( through curl or a Python Script) shouldn't be the first step for customers/admins that they need to rely on. It would be better if there would be at least some fundamental reporting features through the GUI for group usage. (perhaps in Atlassian Administration > groups > open a group > three dots > show group usage).  Kind regards, Christian Winter 

            I couldn't find a separate ticket for Confluence group usage, so I'd suggest adding usage within that product on this same ticket. If there is a separate ticket, please share the link (and link it to this ticket) so I can vote on that one as well!

            Gary Spross added a comment - I couldn't find a separate ticket for Confluence group usage, so I'd suggest adding usage within that product on this same ticket. If there is a separate ticket, please share the link (and link it to this ticket) so I can vote on that one as well!

            William Buschmann added a comment - - edited

            Yeah we do quarterly group audits so we just have the extra step in the documentation to open a ticket with Atlassian since we are unable to access groups ourselves. Just saying, it would definitely reduce the number of tickets you folks receive if you implement something to give us access to this. Happy customers = more recommendations to others. 

             

            +1

            William Buschmann added a comment - - edited Yeah we do quarterly group audits so we just have the extra step in the documentation to open a ticket with Atlassian since we are unable to access groups ourselves. Just saying, it would definitely reduce the number of tickets you folks receive if you implement something to give us access to this. Happy customers = more recommendations to others.    +1

            I have been working on an ongoing group cleanup effort within my instance. It would be so helpful to not have to open a support ticket with Atlassian every time I need up-to-date group usage data. A mechanism within the UI to view/export group usage would be beyond helpful. This ticket is a decade old, but I really hope this is something that can be prioritized. Especially since the data is easy enough for the Atlassian support folks to gather when requested. I'd think it'd be just as straight forward to display with the admin console UI.

            Gary Spross added a comment - I have been working on an ongoing group cleanup effort within my instance. It would be so helpful to not have to open a support ticket with Atlassian every time I need up-to-date group usage data. A mechanism within the UI to view/export group usage would be beyond helpful. This ticket is a decade old, but I really hope this is something that can be prioritized. Especially since the data is easy enough for the Atlassian support folks to gather when requested. I'd think it'd be just as straight forward to display with the admin console UI.

            Paavo P. added a comment -

            Ok, so after 10 years we're still in the phase gathering interests and it says: "This suggestion needs more unique domain votes and comments before being reviewed by our team." - just out of curiosity, how many we're still lacking? πŸ™„

            Paavo P. added a comment - Ok, so after 10 years we're still in the phase gathering interests and it says: "This suggestion needs more unique domain votes and comments before being reviewed by our team." - just out of curiosity, how many we're still lacking? πŸ™„

            +1

            Ian Butler added a comment -

            +1

            Ian Butler added a comment - +1

            To be honest I was shocked to find this was not available. Without having this it makes user and group management extremely labourious.

            I think this should be a core feature - again I'm a bit shocked it isn't already available!

            tim.berman added a comment - To be honest I was shocked to find this was not available. Without having this it makes user and group management extremely labourious. I think this should be a core feature - again I'm a bit shocked it isn't already available!

            wonga added a comment -

            +1 would be very useful.

            wonga added a comment - +1 would be very useful.

              jthomas@atlassian.com Justin Thomas
              bberenberg Boris Berenberg (Inactive)
              Votes:
              316 Vote for this issue
              Watchers:
              183 Start watching this issue

                Created:
                Updated: