Hi Community,
We want to catch the offenders when a "Done" epic is re-opened, either by automation via sending an email to a DL, or a summarized list on a weekly basis via filter subscription (scheduled weekly). I think my current automation rule isn't correct. I am triggering on issue status transition, and then checking if it's an epic type with Done status and resolutiondate < startOfDay(-1). There is multiple issues with this design, I think, it triggers on every single issue transition (hence expensive), and the IF condition is checked after the transition, which I think it's incorrect. I want to catch anything that changed a Done to something else, like In Progress. How should I correct the IF condition? And the trigger if needed?
Thanks!
For the Automation solution, you're making it too complicated. It is much simpler than that. Let's start with your Trigger. It should specify that the transition is From the "done" statuses (whatever those are for your project. That will stop the rule from being triggered on every status transition.
Next you need to check if the transition was for an Epic type of issue.
Then add a Send Mail action (or other type of notification action if you wish) to send your chosen people an email.
You can also solve this with a Saved Filter and Filter Subscription.
There is an operator called CHANGED that you can use to check if the Status was changed from "done" to something else during a time period. You can find documentation on that operator here:
So, you could set up a Saved filter something like
project in (X, Y, Z) and issueType=Epic and Status CHANGED FROM "Done" after startOfDay(-7d)
And then set a subscription to run that report every seven days.
hi Trudy!
That is a much simpler way to implement the automation! thank you! I'll note down the JQL for the filter too if we decide to do that approach (weekly email). Thank you so much!!
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.