Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×Hi all,
We have a Jira Cloud automation rule that is triggered manually from an issue. The rule is designed to backport the issue (basically, it clones the issue with some modified fields).
The current problem is that when a user manually triggers the automation, they only see the notification that the automation is in progress. If the rule fails for some reason, the initiator does not receive any notification. Only the rule owner gets an email about the failure.
What we’d like to achieve is:
The initiator of the manual trigger gets notified if the automation fails.
Ideally, we could also notify all admins or a selected group when the rule fails.
(Perfect solution) A pop-up message for the initiator that says “Automation failed” right after the failure.
Is there any way to configure this in Jira Automation, or a workaround to make sure the initiator and other stakeholders are aware of failures without relying solely on the rule owner’s email?
Thanks in advance!
Unfortunately the only options for notifying on error are via email to the automation owner.
One thing you could consider is adding a comment to the work item when the rule succeeds, so if there's no comment you can tell it failed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Short answer: no, that is not possible yet.
There is an in-progress suggestion to add REST API support for automation rules and audit logs. The endpoints were added for rule management, but not for the audit logs. I recommend watching / voting for this one to see progress and updates...because once there are endpoints for the audit log, creating alerts, dashboards, etc. will become possible.
https://jira.atlassian.com/browse/AUTO-51
Until those are available, the only mitigations are:
And please note well: some rule problems / "errors" do not show as errors in the audit log. This can happen for rules with timing problems, logic errors, service limit violations, Atlassian outages, etc. Thus I recommend a "defense in depth" approach to use various methods to confirm automation health, starting with team members paying attention to check when rules do (or do not do) what is expected.
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.
In your configured automation rule, add an action:
Add Action: Send Email: Click "New action" > select "Send email".
Set the Recipient to the Initiator: In the "To" field, enter: {{initiator.emailAddress}}
Compose the email
Save and publish the rule
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dave Mathijs ,
That is a solution I have been looking at but:
Thanks for the answer !
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.