In case you have automation rules implemented, you can set 2 roles in the automation rule details:
* the owner
* the actor
Now, you can choose, what should happen in case oaf an error:
* notify rule owner once by e-mail
* notify rule owner for each failure by e-mail
* never notify
So, we have a ticket system for incidents, and, when an incident happens, we jump out of the system and use mail again. It's a bit strange here.
Story:
As a rule admin,
I would like to receiver rule errors as a Jira ticket instead of mail
to have rule incidents in my (jira) backlog and notify my team in case of absence that there is a to do.
Approach:
* add customer "no-reply@automation.atlassian.net" to my portal
* set "Automation for Jira" as rule owner
Result:
Whenever a rule fails, I receive an issue which is generated via the e-mail qeue, send by no-reply@automation.atlassian.net.
Now, I can manage the error notification within Jira without changing the system.
Concerns:
This solution has a break of systems. The mail system and qeue is used for this workaround. If there might be any issue in the mail system, the notification might be delayed.
Questions:
Is it possible to raise a ticket if automation fails without changing to mail but to stay within Jira?
Or is this solution stable enough because all jobs run inside the Atlassian eco-system?