Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is it possible to restrict visibility to jira tasks by component or custom field selections?

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.



1 answer

2 votes

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

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events