Can I control write access on custom fields in an issue?

[Lorie Sauriol]

I would like to add a custom field that only three users would have permission to modify, but everyone else can view.

I am using the following link for reference but I haven't figured out how to bring write security down to the field level. Any suggestions would be appreciated.

http://confluence.atlassian.com/display/JIRA043/Managing+Project+Permissions

[Nic Brough -Adaptavist- · Accepted solution]

No, Jira doesn't do field-level security. See https://jira.atlassian.com/browse/JRA-1330

There are work-arounds though. The two I've used are

1. Write my own field, which has a .vm template that limits the edit to the users/groups/roles I want to work with

2. Move edit into the workflow. Remove the field from the "edit" screen for the issue, then go through your workflow adding "edit" transitions that go back to the same status they start from. Include the field on the transition screens. You can then control who has access to the trnasitions by using conditions on the transitions

You can also do it with javascript and I think you can use the behaviours plugin too.

[Neil Arrowsmith]

We do #2 a lot. Especially where we want to restrict who can change the priority of an issue. There we add "Re-prioritise Issue" workflow actions that loop back to the same status, with just the priority field on a screen set up just for that transition.