Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Automation rule not changing fix version

Esther Strom
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 3, 2020

I would like to have an automation rule that updates all children (stories, defects, tasks) in an Epic when the fixVersion on the Epic is changed (including the first time it's set.)

I set up a rule, and the audit log indicates that it ran successfully on the expected ticket numbers, but when I look at those tickets, I'm not seeing the fixVersion populated. (I waited 10 minutes, just on the off chance that it didn't happen immediately.)

Can someone help me out? What have I done wrong with this rule setup? (I'm assuming the "When Value Changes" trigger also includes changing from blank to populated; is that wrong?)

2020-06-03 14_58_49-Project automation - Jira Staging - Vivaldi.png 2020-06-03 14_59_32-Project automation - Jira Staging - Vivaldi.png

 

 

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
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.
June 3, 2020

Hi @Esther Strom 

I just tried this and it worked for me.  Here are my detail settings for comparison:

Trigger: Field value changed

  • Fields to monitor for changes: Fix versions (field)
  • For: Edit

Branch rule/related issues: For stories (or other issues in epic)

  • unchecked "Only include issues that have changed since the last time this rule executed"
  • Action: edit issue
    • field: Fix versions
    • value: Copy from Epic

 

Best regards,

Bill

Esther Strom
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 4, 2020

Thank you! When you first click the Copy From bit, it automatically populates as Current Issue. I assumed the Current Issue was the issue triggering the rule, but I'm guessing because this is inside a branch rule, current issue is the actual issue it's looping on. I didn't realize I could then click into the Copy From and change it to Epic. I've done that and it now works.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, ace, atlassian community event, donation, girls who code, women in tech, malala fund, plan international, kudos, community badge, badge, atlassian badge, International Women’s month, International Women’s Day, women's month, women's day

10 for Change at Atlassian Community Events

Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!

Join an Atlassian Community Event!
AUG Leaders

Upcoming Jira Events