Automation is not working when Jira ticket is in Read only format

[PLaksh11]

Hello Community,

We are using automation rule to update Assignee automatically on each state of issue.

Ex: We are assigning a ticket to custom user picker field person when ticket is moved to done state. and its working. but we have one more requirement that, when ticket is moved to done state then ticket should not be edited and it should be in Read only format. for that we are using Jira properties.

Because of this  automation rule is not working and its not assigning the ticket automatically.

Is there any way that it should allow automation to run when ticket is in read only format in done state?

Thanks,

[Utkarsh Agarwal]

Hi @PLaksh11 

When Jira issues are set to read-only via workflow properties (like jira.issue.editable = false), automation rules can't update them.

The simplest practical workaround is:

Grant edit permissions specifically to your automation user or group even in the read-only status.
To achieve this:

1. Go to your workflow and edit the properties of the read-only status.
2. Add this property to grant permissions exclusively to your automation actor (replace with your automation user's project role ID or group name):

jira.permission.edit.projectrole = <AutomationRoleID>

or

jira.permission.edit.group = <AutomationGroupName>

This allows your automation rules to update issues without changing workflow logic or introducing manual steps.

Note: Ensure only automation actors have this elevated permission for data integrity.

Kind Regards
Utkarsh

[PLaksh11]

Hi @Utkarsh Agarwal 

Thanks for the reply. I tried the below properties but still its not working.

jira.permission.edit.projectrole = <AutomationRoleID>

[Utkarsh Agarwal]

Thanks for sharing the details! A couple of things to check:

1. Confirm the Automation Actor
   Make sure the rule actor (e.g., Automation for Jira) is added to the same project role whose ID you used in jira.permission.edit.projectrole.
   You can verify this under Project settings → People.
2. Using a Group Instead
   Did you try:
   jira.permission.edit.group = <groupID>
   
   (Use the group ID, not the group name—visible in User Management → Groups.)

If the actor is correctly mapped to the role or group, automation should be able to edit even in the Done state.

[Stephen_Lugton]

Hi @PLaksh11 

This is a really hacky workaround:

1. Create a new status e.g. Assign User
2. Set up a transition from Done to Assign User with the condition Hide from User
3. Set up a transition from Assign User to Done
4. Modify your automation:

• Trigger: When work item transitioned to Done
• Transition to Assign User
• Edit Assignee
• Transition to Done