Jira Field Permission

Crystal Rouse March 29, 2024

Is there a way to set permissions against a field in Jira Software and Jira Service Management?  

We have customers that would like to limit editing a field to a user group.  

Thank you for any information or tips on how to make this happen.

2 answers

2 accepted

3 votes
Answer accepted
Valerie Knapp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 29, 2024

Hi @Crystal Rouse , thanks for your question.

It will depend a bit on your use case.

Something I have done before is to have a field on a transition screen in the workflow. Then, with the workflow conditions or validators, you can configure a situation where only users from a certain group can, for example, do a transition where a transition screen pops out with some fields that they need to fill in.

Could this work for your requirement?

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/ 

Crystal Rouse March 29, 2024

Thanks for the tip!

Like # people like this
Valerie Knapp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 29, 2024

You're welcome! Let us know if you need more help. :)

0 votes
Answer accepted
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 29, 2024

Hi @Crystal Rouse 

Not directly; field-level security is not available in Jira.

Natively, alternatives include (in Jira Software)...

  1. Use a Workflow for this; you could have a separate transition that only specific users/groups can use, and then have a screen which has these fields on it on that transition (rather than editable on the main issue screen)
  2. Use Automation - when this field is modified, have Automation check if the initiator is a specific user, or in a specific Group - if not, remove the value, and let the user know this field is not available to them

(1) isn't an absolute, as the user could still modify the fields another way (eg. on a Plan, via bulk edit, etc) - (2) would be more absolute, albeit allowing users to use the field before being warned.

---

You could also consider if an App would work for this? Check out Apps such as...

---

Let us know your thoughts! If you do need more specific instructions to implement (1) or (2), we'd be happy to help :)

Ste

Crystal Rouse March 29, 2024

Thanks for the ideas! We will try them out.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events