Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation Rule fails due to status being a non editable status

Jeffrey Bistrong
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 22, 2023

I have an automation rule that is failing due to the ticket not being editable. Trying to figure out how I can add an exception to this status properties that would allow the automation rule to make the edits it needs to

 

image-20230322-162359.png

1 answer

0 votes
Fazila Ashraf
Community Champion
March 22, 2023

Hi @Jeffrey Bistrong 

You could use the jira.permission.edit.applicationRole property and restrict it to a role where the automation execution account is part of?

Refer more in https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

Jeffrey Bistrong
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 22, 2023

thank you but how would i know what the applicationrole is for the automation user?automation user.png

Fazila Ashraf
Community Champion
March 23, 2023

@Jeffrey Bistrong , you have to look through the project roles in your project and see which one can have this account.

By default, the automation rule actor is in the atlassian-addons-project-access role. Referring to https://support.atlassian.com/cloud-automation/docs/transition-an-issue-with-automation/ 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events