nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to filter the audit log of a specific Automation 'flow'?

Brock Jolet_wkfaaa

Recently Atlassian added this nice status filtering panel when looking at the full site audit log for Automation flows.

Audit filter by status.jpg

Is there a way to do this when looking at a specific flow? That's where I need it.

Especially after the changes to how executions are calculated, we have ended up with many more global and multi-project rules. So, I regularly have audit logs full of 'No Actions Performed.'

This morning I had to navigate through 8 pages of noise in an audit log to find the last time something actually happened.

no actions performed.png

Using the filters on the full audit log for all rules doesn't do much for a site that has hundreds or thousands of rules.

Especially when a rule fails, I should be able to click in from the email I received then just filter for errors. (As a side note, emails generated from Jira Product Discovery failures still have broken links.)

While I'm on the subject of noise, a while back Atlassian made the Automation panel on individual tickets basically useless. Is there a way to disable having rules that don't do anything display here? It seems that every time I'm trying to figure out why something failed, this panel is full of rules that didn't actually affect the current issue.

Automation panel.png

Edit: I also noticed that the status dropdown does not include an option for Aborted which we have unfortunately been seeing more and more often as we start to incorporate Rovo agents.

Accepted answers

Julien Morel_fbmylg

Hi @Brock Jolet,

Andrea's answer matches what I have seen as well: the status filtering is available in the broader automation audit log, but not in the same way inside the audit log view for one individual rule.

The least painful workaround I use is:

1. Go to global automation audit log.

2. Filter by status first, for example Error or Some actions performed.

3. Add the rule name or part of the rule name in the search/filter if the site has many rules.

4. Open the matching run from there, rather than starting from the individual rule audit page.

It is not as clean as a per-rule status filter, especially for noisy global rules, but it narrows the list much faster than paging through No actions performed entries. I would also raise this as product feedback, because per-rule filtering by Error / Aborted / No actions performed would be a very natural place for admins to troubleshoot.

All comments

Andrea Robbins

It's only in the audit log at the moment! I always go to Global Automation settings for this reason, but it may be frustrating for those who are project admins only and not Jira admins.

Ren Takahashi

Hi @Brock Jolet, I would check this from two places, because Atlassian shows automation activity at both the individual flow level and the broader app/space level.

For a specific flow, open the flow itself and use its Audit log button. That should show the executions for that flow, and each run can be expanded to see step details and timing.

For the wider audit log, Atlassian's docs say you can filter/search the table by flow name, date and time, audit log ID, and specific actions/triggers/advanced steps. So if the status panel is only available on the full audit log, my workaround would be:

1. Open the full Automation audit log.

2. Search/filter by the flow name.

3. Add the status filter there.

4. Use the audit log ID if you need to cross-reference a particular run back to the flow's own audit log.

If that status filter is not present inside the individual flow view, it may simply be a UI gap rather than a permissions issue.

Julien Morel_fbmylg

Hi @Brock Jolet,

Andrea's answer matches what I have seen as well: the status filtering is available in the broader automation audit log, but not in the same way inside the audit log view for one individual rule.

The least painful workaround I use is:

1. Go to global automation audit log.

2. Filter by status first, for example Error or Some actions performed.

3. Add the rule name or part of the rule name in the search/filter if the site has many rules.

4. Open the matching run from there, rather than starting from the individual rule audit page.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

audit-log