How to set an automation role

Eszter Somossy
Contributor
February 15, 2024

Hi,

I want to set a role:

When the parent epic is changed to a different (new) epic

And the 

Than change the 'Account' custom filed value

And the 'FinanceID' custoim field value

And the 'Customer ID' custom field value

If the field is on the issue

And if the field is not the same as on the same as on the (new) epic

Could you please help me to build this role?

Thank you.

 

2 answers

0 votes
Humashankar VJ
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.
February 16, 2024

Make it with identifying the trigger and make out the conditions and set actions for the vaues of the custom feilds you have listed

0 votes
Ignacio Aredez GenAI Expert
Banned
February 15, 2024

To set up an automation rule in Jira Cloud that updates custom field values based on changes to a parent epic, follow these condensed steps:

Step 1: Access Automation in Jira
Go to your project > Project settings > Automation.


Step 2: Create a New Rule
Click "Create rule" and select the "Issue updated" trigger.


Step 3: Specify Conditions
Add a condition to check if the parent epic link has changed.
Optionally, verify if the custom fields ('Account', 'FinanceID', 'Customer ID') exist and need updating.


Step 4: Update Fields
Use the "Edit issue" action to change the custom field values. This might require:
Using "Lookup Issues" to fetch the new epic's field values.
Conditional logic to compare and update fields only if they differ from the new epic's values.


Step 5: Finalize
Name your rule, save, enable it, and thoroughly test to ensure it works as expected.


Note: Directly referencing and comparing field values between the epic and its child issues can be complex. This setup assumes basic familiarity with Jira Automation and may require advanced configurations or scripting for precise conditions and actions.

Suggest an answer

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

Atlassian Community Events