-
Suggestion
-
Resolution: Unresolved
-
0
-
Suggested improvements
- 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.
- Pagination for audit log
- Wrapping the large audit logs in Automation for Jira - It would be a better user experinece if the audit logs with webhook response can fit the page width so that users could view the entire log within the page and doesn't require scrolling.
- 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.
- Display issue keys in audit logs without having to click on 'Show more'
- Confusion around audit log duration being execution time vs runtime - The Automation for Confluence/Jira audit log displays parallel/resource execution time, but since it's called duration it can be seen as runtime instead. This leads to confusion with a rule finishing in 5 or 10 minutes but it may actually have 40 or 50 minutes of processing time due to being processed in parallel than totaled at the end.
- At this moment the audit log shows a suggestion on the date (calendar) fields that makes it seem that a date is already added in them.
This can cause some confusion as using the time fields without selecting a date does seem to update the results but gives entries that are not consistent with the dates shown as example.
Please show a different suggestion text or a warning to prompt the user to enter dates on the date fields to be able to use the filtering properly. - Allow automation auditlog time & date formatting -
Raising on behalf of a customer to allow or include the ability to update automation audit log time & date formatting similar to Jira look & feel.
Add more functionalities to the Automation Audit Logs:
- "Filter by Status" (i.e., Config Change, Success, Some Errors, etc.)
- "Jump to Page" (i.e., a text box allowing us to enter the page number to view)
- More page navigation links (i.e., Go To First, Go To Last, more page # options, etc.)
- Extensive logging- What changes occurred under config changes, who made them?
- Automation rule creation & deletion logging - (When, what & who.)
- Ability to filter rules and their audit log based on "action" (example: Send email, Send webhook, Add comment) and if automation performed the action.
- List automation logs entries in order - Originally reported in
AUTO-81, now Closed as duplicate of this one.
- is blocked by
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
ENT-1469 Loading...
- was cloned as
-
- Gathering Interest
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[AUTO-28] Make it easier to navigate Automation Audit Log - add option to search/filter by Issue key, option to view more issues, option to scroll for large audit logs, link directly to the specific component rather than the overall rule
FYI for those comparing the new / old log views at the moment...
Something appears to be "happening" with audit logs for Jira Cloud: in my test site it now takes 2-5 minutes before the log updates / refreshes, even though the rule ran when executed. Perhaps additional parsing / processing / etc. are now happening behind the scenes? I checked and no active incidents are showing on the status pages.
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.
There are times when something errors due to a temporary issue on the action (improper setup, web request server issue, api issues, etc.)... in some cases it is not possible or challenging to re-fire the original trigger with the same exact data. So just wondering if there could be a way to replay the exact rule or pieces of the automation to attempt the actions again on an ERROR. Probably would be good to have this at the action level so the replay could be each action that errored with exactly what was attempted before (understandably, this could be challenging if you are not keeping the data and depending on the action, but figured this might be a good place to ask this question).
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
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.