• 409
    • 17
    • 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.

      Problem Definition

      Currently, we can manage Service Desk customer list by adding user group into the Service Desk project's SERVICE DESK CUSTOMERS role.

      But to manage customers on the Organization level, we will need to add user one by one which is not an efficient way of maintaining the list when there is a huge change in the company's user management.

      Suggested Solution

      Allow Service Desk's Organization to accept user groups.

      Atlassian Update – 5 June 2023

      Hi everyone,

      We are excited to announce that Jira Service Management 5.9 has been shipped!
      This latest release includes the “Share requests with groups" feature, which introduces the capability to share requests with entire Jira groups. Empowering administrators to leverage the Jira's user management capabilities to effectively manage internal customer groups for JSM. This helps create a clearer customer management model to manage both internal and external customers and saves admins from having to rebuild members of Jira groups into Organisations to enable bulk sharing of requests.

      To learn more about the feature, visit the Using Jira groups to share requests guide.

      Cheers,
      Divyanshi Vashist
      Jira Service Management Data Center

      Atlassian Update – 21 December 2022

      Hi everyone,

      Thank you for your engagement with this suggestion.

      We currently have 'Sharing requests with group' on the Jira Service Management Data Center public roadmap. Help-seekers will benefit from a more scalable service desk experience by being able to share requests with groups in the customer portal. This feature will also boost the usability of the existing portal features like voting.

      Please continue to follow this suggestion for further updates in the new year.

      Kind regards,

      Charlie Marriott

      Jira Service Management, Data Center & Server

            [JSDSERVER-4867] Allow user groups to be added into Service Desk organization

            Unfortunately, the new function does not help us. We need the possibility to bind groups to organizations in order not to have to maintain a customer group and a Jira group in parallel.

            The ticket requirement is not fulfilled with this function.

            Karin Hiepe added a comment - Unfortunately, the new function does not help us. We need the possibility to bind groups to organizations in order not to have to maintain a customer group and a Jira group in parallel. The ticket requirement is not fulfilled with this function.

            Sharing Requests with Groups is not what this ticket is about!

            Lots of Automation Rules are dependent on Organisations. It`s not simply done with "We follow a different approach"

            Florian Reichl added a comment - Sharing Requests with Groups is not what this ticket is about! Lots of Automation Rules are dependent on Organisations. It`s not simply done with "We follow a different approach"

            Just a note on the latest update (21 Dec 2022)

            Exposing group names to customers is a very questionable way of solving this problem. Group names are usually named according to naming standards from Active Directory and are often not very readable for a user (for example JIRA-MyCompanyName-ThisDepartmentName-Customers). Might even be that you do not want to expose internal groups to customers at all?

            Organizations are built to give user friendly names to the users and a very straight forward way of sharing tickets. What we are missing currently in this suggestion is the possibility to connect groups to them automatically. If this (simple?) thing would be implemented it would solve the problem for loads of our customers.  

             

            Björn Gullander Eficode added a comment - Just a note on the latest update (21 Dec 2022) Exposing group names to customers is a very questionable way of solving this problem. Group names are usually named according to naming standards from Active Directory and are often not very readable for a user (for example JIRA-MyCompanyName-ThisDepartmentName-Customers). Might even be that you do not want to expose internal groups to customers at all? Organizations are built to give user friendly names to the users and a very straight forward way of sharing tickets. What we are missing currently in this suggestion is the possibility to connect groups to them automatically. If this (simple?) thing would be implemented it would solve the problem for loads of our customers.    

            We have about 400 active users in our instance and already track major groups (such as departments and sub-teams) via Active Directory groups. being able to add groups to organizations means we could people could easily share tickets with their teams, our support teams could more easily associate tickets with specific departments, and it would make organizations a usable feature for instances that have more than 20 people in them.

            Marc Anderson added a comment - We have about 400 active users in our instance and already track major groups (such as departments and sub-teams) via Active Directory groups. being able to add groups to organizations means we could people could easily share tickets with their teams, our support teams could more easily associate tickets with specific departments, and it would make organizations a usable feature for instances that have more than 20 people in them.

            Hi all,

            Thank you so much for your votes and comments. This suggestion is currently being looked at and we’d love to discuss more about ways to improve organisations and what using groups would look like.

            This can entail just chatting over email, or we can setup a 30-minute session to discuss this problem further and how it affects you.

            If you are available to discuss more about this suggestion, please send me an email at umauersberg@atlassian.com. Referencing the ticket and letting me know your company, its size, and how you use Jira Service Management.

            We look forward to getting to understand this suggestion further and marking JSM easier and more enjoyable to use.

            Thanks

            Uli 

            Senior Product Designer (JSM)

            Uli Mauersberg added a comment - Hi all, Thank you so much for your votes and comments. This suggestion is currently being looked at and we’d love to discuss more about ways to improve organisations and what using groups would look like. This can entail just chatting over email, or we can setup a 30-minute session to discuss this problem further and how it affects you. If you are available to discuss more about this suggestion, please send me an email at  umauersberg@atlassian.com . Referencing the ticket and letting me know your company, its size, and how you use Jira Service Management. We look forward to getting to understand this suggestion further and marking JSM easier and more enjoyable to use. Thanks Uli  Senior Product Designer (JSM)

            Phoenix added a comment -

            Is there any news on this, being able to add a customer to a group would be amazing as not all customers have the same
            privileges in their respective organization('s).

            Phoenix added a comment - Is there any news on this, being able to add a customer to a group would be amazing as not all customers have the same privileges in their respective organization('s).

            Not being able to sync an A/D group to an organisation is very poor.

            Andrew Garside added a comment - Not being able to sync an A/D group to an organisation is very poor.

            Concur with previous comments, having Organizations being able to reference groups or leverage LDAP integration is essential to any ITSM instance with a decent sized user base.

            Jesse Ferraro added a comment - Concur with previous comments, having Organizations being able to reference groups or leverage LDAP integration is essential to any ITSM instance with a decent sized user base.

            Yeah we have a 2000+ account instance using this that I am NOT adding by hand.

            Robert Valentine added a comment - Yeah we have a 2000+ account instance using this that I am NOT adding by hand.

            Same. it's almost impossible to make use of the awesome organizations feature when it lacks something this basic... 

            Marc Anderson added a comment - Same. it's almost impossible to make use of the awesome organizations feature when it lacks something this basic... 

              dvashist Divyanshi
              mmuthusamy Moga
              Votes:
              274 Vote for this issue
              Watchers:
              148 Start watching this issue

                Created:
                Updated:
                Resolved: