I want to protect some fields on an Issue of a specific project

[agasull]

I want to protect some fields on an Issue of a specific project so they are not editable for users but automatisions can edit them.

[Christos Markoulatos]

Hi @agasull 

As far as i know Jira Cloud doesn’t have native field-level permissions, but you can restrict editing for some users while allowing others (and Automation) using screens + workflow conditions or a Marketplace app.

Native approach (no apps):

• Remove the field from the Edit screen so it’s not editable by default.
• Create a transition (loop back to the same status) with:
  • A transition screen that includes only the restricted fields.
  • A Condition: User is in project role X or User is in group Y.
• Result: Only those users can edit the field via that transition; others can’t.
• Automation and API can still update the field.

If you need true field-level control:

• Use a Cloud app like:
  • Fields Permission for Jira – Simple role/group-based view/edit control for any field.
  • Field Rules – UI Modifications – Make fields read-only or hidden based on user/group or status.

Some helpful links to get u started:

• Restrict custom field editing by user group
• Use workflow properties

Hope this helps!

[agasull]

Could you go a bit deeper into the native approach? I can’t quite find the edit screen and I’m not sure how to proceed.

[Christos Markoulatos]

Hi again @agasull 

If you want to restrict editing of a field without using Marketplace apps, you can do this with screens + workflow conditions:

1. Remove the field from the Edit Screen

• Go to Project Settings → Screens.
• Find the Edit Screen for your issue type.
• Remove the field you want to protect.
  Note: Some system fields (e.g., Summary, Status) cannot be removed from screens. For those, you’ll need to use workflow properties or an app.

2. Add a Controlled Transition

• Go to Project Settings → Workflows.
• Edit the workflow and add a loop transition (status → same status).
• Name it something like “Update Restricted Fields”.

3. Configure the Transition

• Add a Transition Screen that includes only the restricted fields.
• Add a Condition:
  • User is in project role X or User is in group Y.

Important:
If you’re new to Jira workflows and screens, do this in a test project first, not in production. Workflow changes affect all issues using that workflow, so it’s safer to experiment in a sandbox. Also if u are not comfortable with doing this changes and testing consult your Jira admin or a Consultant.

[agasull]

Hello! I have one more question: where do I add the Transition Screen? I only have 3 Issue Operations: 

• Create issue
• View issue
• Edit Issue

And where am I supposed to add the conditio User is in project role X or User is in group Y?

[agasull]

I created 2 new screens, one for the Edit Issue, called Edit Screen, where I have every field except for the 4 I don't want users to edit, and the other one called Transition Screen that includes only those 4 fields. I also added the loop transition on the workflow but now I don't know how to continue. Thank you.

[Carl Bidwell]

In Jira there isn’t a simple “lock this field” button, but you can get pretty close with a few tricks. The most common way is to remove the field from the regular edit screen and only expose it on a special transition screen. Then you add a condition so only the right role (like Project Managers) can run that transition and update the field. That way, everyone else sees it but can’t change it.

If you need tighter control (like hiding fields from certain groups altogether), you’ll likely need a Marketplace app such as Fields Permission for Jira or Protected Fields, which give you field-level visibility and edit rights.

So the quick win: use workflows and screens to limit who can touch the field. If that’s not enough, an add-on is the way to go. atlassian community

[agasull]

Okey I think I understand what you're saying. The thing is I would need this fields to keep updating only from an automatisation. Will it work this way?

And I got stuck, you can see it in the last message, could you give me more details on how to proceed?