I agree with nathan.given , 73598c92e650 , f45ff7f23a3f, ca242c244352 's assessments and comments that it becomes more difficult to manage Audit Log errors. I just want to reiterate because it has been almost two months, and there are still no fixes yet. 

I also want to second previous comments that these improvements (while looking nice and neat) make it more challenging to troubleshoot the automation using the audit log.

What are the most important things to know about automation rules : 

• I would like to be able to check automation rules where the status is "Some errors" --> so filter on the status
• I would like to see all automation rules that have been done (whatever status) for a certain ticket, I know you can see this on the ticket itself but you can only see the most recent ones --> so filter possibilities on ticket number 
• Also the fact that you need to click on the first block to see the ticket number is a step backwards instead of forward, ideal would be that you see the ticket number in the log list   

I also want to second previous comments that these improvements (while looking nice and neat) make it more challenging to troubleshoot the automation using the audit log.
It is not clear whether the block is expanded or not unless you keep looking at the far right and think for a couple of seconds to associate whether the arrow is pointing right or down.

Also, now we have to click on the first block to see what issue is associated with the log.

The addition of a timestamp is great, though.

I notice that there is another ticket for the changes. https://jira.atlassian.com/browse/AUTO-36

While I appreciate Atlassian's desire to improve the usability of the Audit Log, I agree with 73598c92e650 's and f45ff7f23a3f 's assessment that it is now harder to see the affected/associated issues for a particular automation run.

Here is the reason why - the issue key for every audit log entry is now yet another level deeper:

We have hundreds of entries in some of our automation logs and prior to these changes, it felt like trying to find a needle in a haystack at times.  With these changes, it now feels even harder find the associated audit log entries for a particular issue.

Perhaps if Atlassian added a search capability to the audit log page, or let us filter by issue key at the top of the audit log page, that'd be helpful:

Please make it easier for us to associate audit log entries with issues .

I totally agree with f45ff7f23a3f , this is a step backwards in usability. Yes it is more eye-candy, but we are more looking for a quicker/easier way to find the root cause of a problem solving.

Greetings, and yikes!

In my opinion...The current set of "improvements" to the automation audit are quite poor and a step backward in usability and effectiveness. 

Previously we could open the log details and with a glance see which rule components ran and the associated issues.  We could easily see when conditions were met or not.

Now we must pause and expand-each-step's-details to see the impacted issues, and it is no longer easily visible which conditions were met.

What do others think?

Kind regards,
Bill

As a part of these enhancements, have you all considered adding a manual replay of an item in an audit log?  I may have discussed this with some of you in the past, but I did not see a work item.

We've released the following filters:

• Status (global admins only)
• Audit Log ID 
• Trigger 
• Action 

We've also done pagination and you can copy a shareable link of the filters selected. 

It would be great if audit log items had a shareable URL (have audit log ID as a parameter in the URL or date range like JQL) so that we can send it via chat, ticket, etc

e00fec873fe4  - 

Don't know if this is already included here, but if you're still scoping this out, it would be great to see in the audit log for config changes, what it was that changed!

That it changed is useful, but not perhaps as useful for troubleshooting as what it was. 

(I am picturing some kind of diff perhaps?)

Also maybe something for later versions.... config-as-code please!? The ability to read rules from a Bitbucket or Github repo would be amazing. That way changes to rules could be managed / reviewed etc the same way we do production code. 

BTW - I <3 Jira automations!! I make work, so I don't have to. 

Happy Friday all!

+1 we need really much to search by key.. not by audit log id, it is useless...

Would be nice to have the audit log ID exposed in the history record entry where A4J has made the change so that I can pull the ID from an issue's history and search that in the audit log

+ 1 please. It would be great to filter by trigger as well - eg. to see all rules in a project automation listing OR global automation listing of rules that trigger by "issue created" or "manual trigger", etc.

Thank you in advance

I would absolutely advise to be able to filter on issue key, issue number

I definitely agree that this is essential for Jira admins.

I think this is essential as a Jira admin to have access to such filters to quickly find why an automation didn't work.

I would like to be part of the EAP if possible!

Thank you,

I would be also useful to enable search by error message (or part of it) - to find other previous same or similar occurrences of the error - in 1 but also all automation rules.

YES, PLEASE!
When someone tells me an automation seemingly didn't fire for a specific Issuekey, it's often several days after the fact and I have to scroll through several audit pages looking for automation information related to the issue..  The ability to filter on a specific IssueKey would be INSANELY useful for troubleshooting the history of the specific example presented to me.

Filtering rules by type of action is needed in analysis of bugs with automation rules - example what recently happened with "Edit request type".

When having a lot of automation rules and something like this happens (rules are failing for hours)... we should be able to quickly find all rules that execute certain action to determine impact / data loss - in this it was "Edit request type". But it is same for all the other action types.

Hi, facing the same issue - please confirm by when the issue will be fixed by Atlassian. Thank you.

Yes, adding automation rules to the many business workflows and then recovering / replaying them after an incident without a comprehensive and functional audit log is very time-consuming or even impossible.

In light of most recent incidents, this would solve many critical situations when all failed business-critical automation can be identified while the incident takes place and necessary actions. For advanced organizations moving forward with an increasing amount and dependency on automation, it becomes critical to have such functionality. Expect this functionality will be prioritised in near future.

It boggles my mind that there's been an open enhancement request for simple search that's more than two years old. this is basic, basic functionality. 

eeb2e5a08fc6, any update on the timeline for these improvements? We desperately need at least status filtering in Cloud. There are way too many rules running and for errors, if we cannot jump into the audit log immediately when we get an email notification, the errors are buried hundreds of pages deep. Status filtering will also help us know when there were configuration changes and who made the changes. Hopefully that piece is rolling out soon and then you can iterate to introduce all of the rest of the asks on this suggestion.... all of these would greatly improve automation. I guess filtering did exist in server according to this: https://confluence.atlassian.com/automationkb/using-the-audit-log-1130727684.html

I'm having to hard code Log actions to show where the rule enters If and Else-IF blocks. I'm finding the If/else block Passed message at the end of the Audit log list of actions. 

...
If block
Assets field condition failed (system message in Audit log)

Log action
Log
Else-if passed (I hard coded this message in my rule)

... multiple edits and Log actions

If/else block
Assets field condition passed (system log at the end of the Audit log)

No wonder I have a hard time deciphering these logs!

https://community.atlassian.com/t5/Automation-articles/Jira-Cloud-automation-Manual-trigger-rules-are-moving/ba-p/2314046

Now that Automation Rules are being moved, this functionality is required more than ever.

On the individual issue 'Recent rule executions' seems like it will be removed. Which is required to have a quick in-issue view of what's been run / not run on an issue.

The replacement link to the 'Project Settings > Automation > Audit Log' is going to be so much worse without the ability to actually search through the data.

Seriously what is the point of collecting thousands of logs if you need to individually click 'Show more' on every one to find what you need?

+1

current ability to go through these logs to find errors is VERY poor

With this one being almost two years old, and Jira looking to be the best-in-class ITSM tool it is; this is a big one.

Jira admins need this one. I hope it gets some love soon.

https://community.atlassian.com/t5/Automation-questions/Where-is-the-Automation-Audit-Log-stored/qaq-p/2237219

Yes Please! To Everything added to the Description yesterday!  thank you @MonaS especially these:

• *** Users would benefit from the ability to perform searches in the audit log of a rule for multiple purposes, specially if their execution count is too high to look through each entry.
• Add "See more" button to audit log results - When an automation rule affects a large number of issues, it is impossible to see in the audit log a list of all affected issues because it is truncated.
• "Jump to Page" (i.e., a text box allowing us to enter the page number to view)
• "Filter by Status" (i.e., Config Change, Success, Some Errors, etc.)
• Extensive logging- What changes occurred under config changes, who made them?
• New one: Be able to roll back changes to an Automation if recent changes break

+1

This would be extremely helpful for digging through logs. Especially because right now we have to click through pages of logs to get to certain timeframes. Recently, I was looking for a log that was like hundreds of pages in and it took forever and was extremely tedious. I'd like to be able to search by things like: issue key, rule id, rule actor, date range, project, etc.

Unless I am missing something, audit logs related to Jira Automation are managed separately to the Jira logs, and the ability to export the logs is lacking.  I believe with the server version it was possible to access the logs through an API.  Since we are able to add log comments as a function of Jira Automation, having an ability to query, or at a minimum export the logs would be beneficial with root cause analysis and troubleshooting.