I have an automation rule which triggers on several transitions like so:
This works perfectly for all transitions besides when the issue is transitioned to Discarded. As far as I can see no other automations are in play.
Any ideas what is going wrong?
Hi Nils - Welcome to the Atlassian Community!
What does the audit log say when it is Transitioned to Discarded? Are you saying that the automation doesn't fire? Or that there is no action performed?
Hi John,
strangely the transaction does not show up in the audit log at all. Consequently, no other parts of the automation are being executed either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would check the Rule details and make sure the Allow rule trigger check box is checked. It might be that another automation is firing first and this one is not even firing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There shouldn't be any other rules firing before this one. I did test it with the box enabled nonetheless and the result is the same: The transition to Discarded does not show up (not even in the audit log). Transitioning the same ticket back to New & Backlog does successfully trigger the automation as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe create a copy of the rule and clear out all of the other statuses except Discarded and try the rule for a single project that you are using.
Then change that to multiple projects or global and see if it still works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nils Kunze
Adding to the ideas John suggested...
Do you have a custom workflow, perhaps related to the status Discarded? If so, there is an open defect that when you have a custom event on a transition, the Issue Transition trigger does not fire. The work-around is to remove the custom event.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.