For example:
Story B under Epic 1, it has 3 story points, Epic 2 has no story points been entered
Change Story B from Epic 1 to Epic 2
Check Epic 2, will its story points have been updated to 3
------------------------------------------------------------------------------
Check Epic 1, its story points will be updated to 8 instead of 11
In this case, I know configure Scheduled in Automation can implement it. But I find once config Scheduled, I have to set it how often the it will be triggered. Even if during the time, no one story has any its Epic' changes. As long as the set trigger time arrives, this rule will be automatically triggered.
In order to save resources, I would like to implement this rule to be triggered only when the Epic of the story is updated. How should I configure this automation?
Thanks all guys' responses!
Hi @Ni Zhang -- Welcome to the Atlassian Community!
Your rule could use the field value changed trigger, watching for changes to the Parent field, and then use the changelog smart value to update the new and old parent Epics using branching and the Lookup Issues action. This is a very common community question, and if you search will find several example rules.
And, please note well: what you describe is only one of the possible scenario. There are several others, so decide which ones you want to handle as the different rules will have different triggers and logic. For example:
Kind regards,
Bill
Hi @Bill Sheboy
Thanks your reply.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.