Hi All,
This is a simple question. But where is the documentations pertaining to the definitions of each Status of an Automation execution in the Audit log.
Hi @ChristopherChilds, thanks so much for your question! My name is Kevin, and I'm responsible for maintaining the Jira Cloud automation documentation.
As @Nic Brough -Adaptavist- said, the status definitions aren't in the docs. However, we do define them in product on the Audit log screen:
Just wondering if there was anything in particular that you were looking for, that isn't described there? If so, I'd be happy to add it to the docs.
Once again, that's for your feedback!
Thanks Kevin!
I must admit I've never clicked through to see that. Atlassian have chosen status names that make sense to me without explanation. Great to know there's more detail directly online without having to go to documentation, everyone should do that more!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kevin BuiThank you very much. This is what I wanted. @Nic Brough -Adaptavist- I also did not see this in the Server editions too.
I am going to present Jira Automation to the company and so I know that this could be something which comes up. As many users are not developers and may not be familiar with some of the terms.
I had some follow-up queries, but I now see that there is a way to update the limits for Server/Data enter edition:
https://confluence.atlassian.com/automation/automation-service-limits-993924705.html
I think this I will be implementing more monitoring about current limits.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kevin Bui and team
TL;DR our statuses explanation list differs from yours in a misleading way: our list doesn't have ABORTED, and our SOME ERRORS explanation matches exactly your 2023 ABORTED explanation...
---
At writing, our statuses explanation list is different from what you posted here in 2023. I'd like to draw your team's attention to our "SOME ERRORS" automation status explanation which matches that of "ABORTED" in yours.
In ours, "ABORTED" does not exist.
Trying to investigate intermittent SOME ERRORS statuses on an automation rule that for the most part runs successfully, and the "...the rule was disabled, deleted or re-configured while it was running; or you may have reached your execution limits" explanation for our SOME ERRORS status had me looking at our automation usage page which hovers at only 2% used monthly for the past six months.
I'm thinking now that the root lies somewhere in your 2023 SOME ERRORS "...some actions in this rule produced errors. Please check your rule configuration." explanation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are no docs for the status - the status names pretty much are the documentation. When it says "config change", someone has changed the automation. When it's "in progress", the automation is currently running. "Success" means "ran without problems". And so on.
What are you looking for from this documentation?
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.