Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

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

Jonathan Smith
Jonathan Smith
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
Aug 09, 2022

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.

Thanks,

Jonathan

Answer
Watch
Like Be the first to like this
317 views

1 answer

2 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Aug 09, 2022

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"

View More Comments
Matt Doar
Matt Doar
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Aug 09, 2022

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

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira Core
Jira Core Server
TAGS
AUG Leaders

Atlassian Community Events

See all events