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
I have a group who wants to restrict viewing permissions to components (or a custom field by "sub type") while still giving Create and Edit access to the Jira project. Is this possible?
I have already suggested breaking out the content into separate Jira projects but I am doing my due diligence for the user.
No, it's not possible to do this.
You can only restrict issue visibility by using security levels. You could set up something convoluted about setting security levels with Automation, based on other fields, but it is complex and unwieldy, and the complexity usually means mistakes will happen and people will get to see the wrong thing. I'd always push "separate projects" over "automated security levels"
Right. From our experiences, it will work then break at some point and be more effort to fix it. Separate projects for different access permissions is the way to go