Restricting Edit Access to Approvers Field Based on Approver Group (Considering Native Limitations)

[gollapudi sidhvi]

Description:

I have a workflow where an Approver Group field is automatically populated (via automation) with a specific group when an issue reaches a certain stage.

Requirement:

Only users who belong to the populated Approver Group should be able to modify the Approvers field. All other users should be restricted from editing this field.

Challenges / Existing Limitations:

1.No Field-Level Permission Control

Jira does not natively support restricting edit access to a specific field based on user groups or values stored in another field.

2.Approvals Configuration Limitation

In workflow approvals, we can configure either:

Approvers (user picker)

Approver Group (group picker)

but not both together in the same approval step.

This creates a trade-off between:

Group-based control

Flexibility to manage individual approvers

3.Field Value ≠ Access Control

Even if the Approver Group field is populated dynamically, Jira does not enforce permissions based on that value.

4.Multiple Edit Entry Points

Users may still be able to modify the Approvers field via:

Edit Issue screen

Other workflow transitions

unless all paths are explicitly controlled.

Goal:

Looking for a robust approach to:

Restrict modification of the Approvers field to only users in the selected Approver Group

Eliminate all alternate ways of editing the field

Maintain a controlled and auditable approval process

Achieve this preferably using native Jira capabilities (workflow, screens, automation) without relying on third-party apps

Any recommended design patterns or best practices to handle this scenario effectively would be helpful.

[BURAK BAL]

Hello,

I recommend creating a new global workflow transition(from any status to any status). It will act as a button on the user interface and be located under the automation button. You can associate the transition with a new screen that includes only the "Approvers" fields. And you can add a condition to the transition, and only users in the Approvers field can perform the actions. Then you should remove the Approvers field from the Edit issue screen on the screen scheme.

Hope it will be helpful.