Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Update several Epics Story points with manual trigger

Hello,

I created 2 automations to update the Epic story point field with the sum of its story points after an update on one of the stories. One of automation is to update the story point field and the other (with a different filter) is to update a custom field "story points done" on the Epic.

This is working fine but I would like a manuel trigger to cover less frequent scenarios that will not be managed by my automations : moving a story from epic to another, deleting a story, etc. 

This manual trigger will take a group of Epics (found by JQL based on the fix version field) and for each epic do the same sums to update the fields.

I'm not sure how to do that with the lookup and/or branch feature of JIRA automation.

 Any idea?

Matthieu

1 answer

Hi @matthieugd 

This is more challenging as you cannot nest branches or directly call one rule from another...however you can trigger one rule from another to do this.  How about this:

  • For your manually triggered rule, for each impacted epic add a special comment: "recalc story points done, requested {{now}}"
  • Add a second rule, triggered on comment matching the pattern and checking the issue type as epic, use your logic to update the custom field.  Please note this rule is triggered by the other, so you need to check the option under rule details: Allow rule trigger.

By the way, for your edge cases you may not need the manual rule for clean-up/catch-up. Instead if you can find a way to catch the event with a trigger then you could also add the same trigger comment to have the epic update.

Best regards,

Bill

Thank you Bill, I will give a try !  

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Automation

Announcing the Jira automation template library!

Hi all,  After many months of work, I am delighted to announce the launch of the Jira Automation Template Library!  The Template Library is a new website dedicated to all things Jira au...

1,258 views 20 27
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you