Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I limit view access for certain fields in an issue?

I have a couple of users accessing an issue, however I would like to:

- hide a couple of custom fields from certain users. 

OR give view access to certain users

1 answer

1 accepted

0 votes
Answer accepted

You can not.  Jira does not do field level security (in the interests of openness, sharing and because it's quite hard for little reward).

You'll find some attempts at it done in javascript and Behaviours, but these don't truly hide field content, and there are ways around them that are a doddle (they're ok for presenting different interfaces and playing tricks like "hide if", but they are not in the slightest secure)

There is an add on by QuisApps, called "field security" which does it properly.

Thanks Nic, 

This feature would have surely made life easy.

On another note, can I configure view/ edit access for a screen?

It actually makes life hard, as you end up with people having different views of issues and talking cross-puprose because they are missing information the other can see.

Edit access is possible, but not by screen, it's done by project.  You can grant (or not) "edit" access to the issues within a project in the permission scheme, which allows you to do it by group, role (strongly recommended), participant type (assignee, reporter, etc), fields, and so-on.  To get very clever, you can also modify it further by using "workflow properties"

View access is done in even more layers.  You grant "browse" access to users in the permission scheme.  You can modify that with "workflow properties" (but this is clunky and usually doesn't do what you need or expect), and "issue security" which does work exactly the way you expect.  (Set a security level field, and the issue is limited to view by only the people who match the rule for that level)

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you