Block edit fields that use in automations

Xeila April 15, 2024

I need that some field that use in automation not modify by user agents but is necessary that automation modify this fields.

In my organization have two calendar type, normal or intensive. When work in summer have the intensive, and i need that de open issue change this field but i don't want that the user change this value. 

is possible that only automations modify the fields ?

1 answer

0 votes
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.
April 15, 2024

Hi @Xeila 

Is it only certain fields, or all fields?

You might be able to do it using a workflow property per Status if it's all fields, by blocking the permission "edit". Check out the property jira.permission.*


Aside from this, field-level permissions aren't available natively - options are...

  • Hide the fields; remove them from the Screen, and just have them in the background
  • Use issue operations - see Manage screen schemes - to have two separate screens, one for "view issue", which these fields would be on, and the other for create/edit

^ These make it much harder for a user to edit the fields as they're not available on the Screen - but it's not impossible, they can still do it via list views, bulk edit, etc.


Other options to try and limit changes include...

  • Using Automation to check if the user is allowed to make changes, and reversing it if not
    • This doesn't "stop" the edit - it would just change the value back to the previous one if the user isn't authorised to make the edit
    • I'd also have a way to warn users if this happens - eg. a comment or an email
  • Look for an App on the Marketplace that provides field-level permissions


Let us know your thoughts!


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events