-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
15
-
4
-
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.
Suggestion
Following the addition of the 'Organizations' feature in JSD-270
Example
User A is set up and is added to Organization A
User B is set up and added to Organization B.
A new Request Type called Request A is set up
Permissions are added to Request A so that only Organization A can view it in the portal
This means that User A can see this Request Type when they login to the Portal, but User B cannot
Why it would be useful
This would be useful as we are currently dealing with multiple clients within a single Service Desk. The ability to do this would allow us to personalize a portal for each client that we have.
- relates to
-
- Closed
- links to
[JSDSERVER-4486] Ability to show/hide Request Types based on Organization Membership
We have a need to display certain groupings of options on our service desk dependent on the lifecycle of product delivery, so I need to be able to hide/show groups of options for a time period to a select band of clients. Or at a minimum, allow permissions to show/hide groups and clients can be added/removed once they are past the due date.
We are using this feature in Extension for Jira Service Desk. However we are migrating to the Cloud and the vendor has not recreated this feature in their cloud version. I am noticing that vendors seem to be lagging in migrating their code to cloud. Is Atlassian creating the APIs for these vendors to use?
Hi,
More than 4 years without any solution, so we decided to create ours. You can find this feature in our app Feature Bundle for Jira Service Management. Documentation is available here.
Appsvio Team
This issue is over 2 years old. Really Frustrating to see Atlassian have this in "Gathering Interest" status. I get why, don't have to explain. On the flip side, this should have been an out of the box feature. Add a customer to a group, its crazy that feature isn't part of service desk for customers.
So our scenario is what we have a load of both internal and external customers serviced by the same support team. I don't want the external people to be able to view all our messy internal issue types - just the few external ones we frequently deal with. I want them to be able to use the portal and leave customer sat ratings, though. Seems like we need some sort of 'profile' by organization.
+1