Forums

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

Im searching for an automation

Vivek Challa November 16, 2023

I have a tree issues, 3 story under Epic.
one of the story is in done status and Epic Status also is in Done, if  I take any change in any field of the ticket(story), which is in done status, that story status should change to ToDo from Done automatically (if i made any update in any field in that issue), and here I want that Epic status also should change to ToDo from Done automatically.

this is the automation i have done

TRIGGER: Issue Updated
CONDITION: Issue Field Condition
Issue Type is one of <select all your standard issue types>
CONDITION: Issue Fields Condition
Status equals Done
ACTION: Transition Issue
Status: ToDo
FOR EACH Related Issues: Parent
CONDITION Issue Fields Condition
Status equals Done
ACTION: Transition Issue
Status: ToDo

but here i have another obstacle, here i want this action to be done when any changes takes place in summary,description and status only. here i have taken the condition "issue field condition". i have given summary equals to  value {{changelog.summary}}. but it is not giving expected result.

 

https://community.atlassian.com/t5/Jira-Software-questions/automatically-copy-the-status-field-in-parent-ticket-as-sub-task/qaq-p/2534428

1 answer

0 votes
Trudy Claspill
Community Champion
November 16, 2023

Hello @Vivek Challa 

I added a reply on your original post (the one you linked in this post).

If you want this change to occur only when specific fields change then I recommend you use the Issue Field Changed trigger instead and create a separate rule for each field you want to monitor.

The reason I recommend this is because using the Issue Updated trigger will have this rule triggered for absolutely every change to the issue - comments, status, summary, description, watchers, assignees, links, and so on.

While automation doesn't count in you usage rules that are only triggered but perform no actions because Conditions are not met, it would be less system intensive to have three separate rules (one for each field) that are triggered less frequently.

 

If you insist on using the Issue Updated trigger, then to evaluate if a particular field has change you will need to use the Advanced Compare condition and compare the To value and From value of the changed field.

 

Screenshot 2023-11-16 at 8.35.49 AM.png

Refer to https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog--

However, it does not appear that every field actually gets recorded in the change log, and Description is one of the fields that is not included.

So, I don't think this is the right solution for you.

Suggest an answer

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

Atlassian Community Events