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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
For instance, I have a department that has to see only 1 specific request type while some other users may see every request in our service management software.
Welcome to the Atlassian Community!
The only way to do that would be to have different projects for each department.
Thank you!
I was thinking about going through the following steps:
Could this possibly resolve the issue? I have not tried it yet but I plan to test it soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That will work as you describe, but only for the issues behind the requests.
Your customers will still be able to see, and create, requests of any type. They just won't be able to see the issues the agents are working with. But most customers don't get to see the underlying issues anyway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I do not intend to limit the ability to interact with requests that customers have created. So, I guess I'm going with the security levels setup.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.