How to Track automations executions per type of issue and per project

[Térence LECROIX]

Hello,

We'd like to know how many automations have been executed for a specific issue.

The point would to be able to estimate an average automation for a specific type of issue in specific project from the creation of the issue until its closure.

Is someone managed to get this information ?

The audit log provided by Atlassian doesn't allow gather such information which would be very usefull in order to be able to control and manage properly automation executions.

Thanks in advance !

[Bill Sheboy]

Hi @Térence LECROIX 

Short answer:

I do not believe that is possible, even for an individual Jira issue.  A mitigation may be to accurately document your rule usage, such as in Confluence, to track which issue types teams anticipate could be impacted by rules; then use this documentation with the Global Rule Usage data to make decisions.

Longer answer:

There are several reasons this information may not be available for customer analysis...

The automation, audit log details available to customers show the issues accessed by rules...up to a limit.  They do not show all of the issues in the UI when there is a large batch, as the list of issues is truncated in the log.

And at this time, there does not appear to be a public REST API function to export automation audit logs for external analysis.  (Although without this API, is unknowable if the audit log does indeed contain the list of all issues accessed :^)

Individual issues have history, and when a rule makes changes to the issue the change log notes that, referencing the rule actor.  And so theoretically one could read the change history for each issue to determine rule impact.  However, the default actor is the Automation for Jira user, but if any actors in rules have been modified the change history will not indicate the actions were from a rule.

With the changes to the automation packaging model, what counts toward the limits has changed.  And so some things which access issues will not necessarily appear in the logs.  For example, using the Send Web Request action to search for issues using the Jira REST API.

The mitigation I noted earlier, along with actively managing automation rule usage may help with what your teams are trying to observe.

Kind regards,
Bill