-
Suggestion
-
Resolution: Fixed
-
None
-
None
-
459
-
6
-
Description
Now it is only possible to add single users to an organisation in Service desk. This is really a clumsy way of handling the members of organisations. Normally you would like to use groups to handle all permissions in JIRA.
The governance of users should be able to handle in Active directory only, but with this limitation you require manual steps in JIRA when adding/removing/changing membership of an organisation.
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, including support for automation. 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
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
- duplicates
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-5072] Being able to add groups to organisations
Since the new "Share requests with groups" feature introduced in JSM 5.9 is not fulfilling all the requirements for which customers voted on this closed suggestion, I have created a new enhancement request:
If anyone is interested in this, please vote for it and add yourself as a watcher. Thank you!
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.
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 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)
Not having the ability to add Groups to an Organization creates a tremendous amount of overhead for on boarding and off boarding users. This feature is basically unusable in its current format.
@all here. IMPORTANT NOTICE:
Please upvote JSDCLOUD-4867 Allow user groups to be added into Service Management organization - Create and track feature requests for Atlassian products. as it is encompassing this as well. Both are gathering interest which is just not giving a correct idea.
Thanks a lot!
Please take a look at [Tinker for JSD|https://marketplace.atlassian.com/apps/1222917/tinker-for-jsd?hosting=server&tab=overview]
Unleash your customer portal without any unnecessary barriers to entry. (Anonymous Access) by allowing your customer to access without log in and also takes care of spam by securing customer portal with reCaptcha v3.
Features:
- Public Customer Portal (Anonymous Access)
- Public portal Creation behavior
- Auto create user by email
- Use public user to create
- Auto add Email field to portal fields
- (without modifying request screen)
- Limit publicly accessed Service Desk portals
- Secure Public Portal with reCAPTCHA v3
- Adding Google Analytics to Customer Portal
- Organization Association with Email & Groups
- Add Customer Portal Buttons
- Customer requests CSV exporter
- Add columns to customer request grid
- Better portal grid view
Looking forward to better Tinker Jira Service Desk to fit your needs
https://marketplace.atlassian.com/apps/1222917/tinker-for-jsd?hosting=server&tab=overview
As others already said, the current implementation is not what was requested here.
But anyway, personally everything that deals with "Jira Groups" should have the ability to limit / exclude certain groups otherwise this can't be used in production for various reasons! (JRASERVER-61856)
This would make sense in a B2B context. But in every in-house context people for example will have a jira-software-users group, because they are also regular Jira users (not only customers!) and they shouldn't be able to share requests with e.g. > 100 of people.