Field permission and Field value permissions

[Jason Turner]

I have two related questions.

1. Is it possible to restrict either visability or editability of a field. I want some users to be able to edit the field but not others.

2. I want some user to be able to select some values of a field but not other value. For example. I want one group of users to not be able to set sevirity of an issue to 1 or 2.

Perhaps these are not accomplished with features of the product but just how fields are offered/structured kind of a work arround to accomplish the same goal which I am fine with.

[Nic Brough -Adaptavist- · Accepted solution]

1. No. Jira does not do field-level security. There are plugins that do a lot of it, but you can't use them in OnDemand. There are some workarounds at https://jira.atlassian.com/browse/JRA-1330 though (the obvious one is to remove fields from "edit" screens, and then hack your workflow to have transitions which can be protected with conditions and go through screens which do have the fields on them)

2. Not really. There's nothing built-in to do this, but you could try some javascript tricks. Again, you could find plugins to help... except you can't use them in OnDemand.

[Allison Tait]

Is JIRA now capable of field level security?

[Nic Brough -Adaptavist-]

No. Atlassian don't rate the usefulness particularly highly and have no need or desire to stomp on their partner's offerings on the subject.