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
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well for example, it would be very practical to have a special field for internal notes when working on a project with customers or third parties.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.