You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have request type and multiple domain customers and from that I have a request type which is specific to one domain customer. So, Now I want to restrict that request type to be hidden to all of the other domain customers and only visible to that one particular domain customers. Need a quick support on this. Appreciate your quick response in advance.
Welcome to the community. In JSM, you can control (lockdown on project access) by using "Customers Permissions" to essentially prevent users from seeing the project and its associated requests submission UI via the portal.
However, out of the box, you cannot restrict which service (request submission) are available to your customers in the portal UI. You will need a third party paid add-on to provide you with the ability to restrict request type visibility for your customers.
Here is an possible add-on that you can take a look, but I am not sure if it can provide this type of control for the CLOUD env yet. I know it is available for the on-prems (server) env - https://marketplace.atlassian.com/apps/1212161/extension-for-jira-service-management?hosting=cloud&tab=pricing
Lastly, there is an existing outstanding Atlassian enhancement ask for this functionality - https://jira.atlassian.com/browse/JSDCLOUD-195
Currently, if you want to restrict request types against customers, you will need to create multiple JSM projects and control access within each project.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
This is not possible out-of-the-box, you need to create two separate customer portals or to use an app:
Hope this helps,
what Mohan meant is
1. There are two issue types (A and B) in the same JSM project
2. Tickets with the Issue type A in Project P should be visible and actionable to Agents in Group internal-Agents (Company Domain Users)
3. Tickets with the Issue type B in Project P should be visible and actionable to users in Group External-Agents (Support Partners/Third Party folks)