You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I know there's a significant amount of conversation around the aggregation of story points onto Epics. I'm able to monitor the Story Point field to trigger a rule that runs in the context of that Story's Epic and Sums all the Story points onto an epic. No Problem.
What I'm trying to figure out is how to catch the event where a Story is removed from 1 Epic and added to another in order to make sure both the Previous Epic and the Current Epic has their aggregated Story Points recalculated. It seems to me that I can monitor for a Story being updated using the "Issue Updated" trigger (because I can't listen only on Epic Link Field change anymore), In that case I can identify the "New" Epic and reaggregate the Story points on it, however I'm unable to identify the "Previous" epic. Changelog doesn't seem to be my friend here. I'm also not loving the idea of listening for any "Issue Updated" event as that will trigger many more automation runs that I'm interested in.
Does anybody have any ideas? I'm stuck
Hi @Patrick Kramer,
I agree with you about triggering automations from "Issue updated", it's not ideal as it can trigger a lot of automations. I'm afraid it's the only option to get what you want though, see the example rule below:
You can use the following smart values:
Hope this helps!