In JIRA cloud, how to restrict a field only can be changed when the status is change to closed

[Benjamin Zhou]

In JIRA cloud, how to restrict a field only can be changed by one user and one group when the status is change to closed.

For example, I want to these 2 fields "Number of Users" and "Effort in Hours" only can be changed by one user and one group when the status of this task is "closed"

Thank you in advance for your help.

[Gor Greyan]

Hi @Benjamin Zhou

Sebastian’s approach is the one I would use as well.

Jira Cloud doesn't have native field-level permissions that make a field editable only for a particular user/group based on status.

A practical solution is to keep these fields read-only during normal work and expose them on a dedicated transition screen when moving to Closed. The transition can then have a condition restricting it to the required user and group.

If everyone else must also be able to close the work item, having a second transition to Closed without those fields, as Sebastian suggested, is a clean way to handle it.

Regards,
Gor

[Benjamin Zhou]

@Gor Greyan I am sorry my issue is I do not want to change the workflow.  I mean I don't want to add one more transition.

[Gor Greyan]

@Benjamin Zhou

Understood. If you don't want to modify the workflow or add another transition, then native Jira Cloud doesn't provide this capability.

Jira doesn't have field-level permissions that allow you to say: when the status is Closed, only User A or members of Group B can edit these two fields.

If you have ScriptRunner for Jira Cloud, you could look at Behaviours as an alternative. Depending on the field types and screen involved, a Behaviour can make the fields read-only based on conditions such as the current user/group and work item context.

Regards,
Gor

[Sebastian Krzewiński]

Hi @Benjamin Zhou 

I would try to solve this in that way:

• fields is RO on view screen
• to Closed status there will be a 2 transitions
  • 1st one with condition that user and group can see it and with transition screen with fields
  • 2nd one with condition to cover all other cases without transition screen (if this transition is necessary)

Regards,

Seba

[Benjamin Zhou]

@Sebastian Krzewiński thank you for working on my request.  Due to I can not change the workflow.  Do you have another way?