What would make it easier to test and troubleshoot your automations?

[Charlie Gavey]

Hi Community!

Charlie here from the Atlassian Automation product team. We're working on making it easier to test & troubleshoot your automation flows, and we'd love to hear your feedback.

If you have any thoughts or suggestions for how we can make this easier for you, leave a comment below, or book time for a chat with the Automation team here: https://calendly.com/cgavey/automation-feedback?month=2025-12

Thanks,

Charlie

[Chris Rogers]

Hi @Charlie Gavey

A few thoughts:

• Being able to add a comment in an automation rule to explain what a particular section of the rule is meant to do.  Audit log entries work for this today, but feel a bit clunky to use this way; I don't necessarily need to put data in the audit log for review (they're great for that), just explain to anyone looking at the rule "This lookup does this and then we use the value in this way".  Using the audit log action for this also eats up a valuable component
• In Global Automation, being able to filter by issue key and status of an automation run at the same time
• From the Project Automation view, being able to search the audit log by the issue key; Jira Administrators are able to do it from the Global view above but more and more project administrators are asking for tools so they can troubleshoot their automations themselves.
• Filtering options for the Automation -> Recent rule runs section on the issue view.  I think it would be useful to be able to filter out automations that triggered on a particular issue but didn't actually do anything (think signal to noise ratio)

[Alan Bruce]

Here are a couple of things that I know others have talked about:

• Have the ability to save snippets of an automation that will be reused in other Automations
• Have the ability to automate documentation of the rule into Confluence. 
  • Being able to compare rules
• Some sort of 'Preview' of what the rule would do if activated
  • maybe choose a key and then layout what rules would run and what the end result would be
• Fully agree on being able to look up the Automations that did 'execute' on a specific key. Super annoying having to search through Audit logs
• Have the ability to sort the Automations by the Rule Owner. Currently I can only sort by 'all' or 'me'.

[Piyush Annadate _ACE Pune_]

Hello @Charlie Gavey ,
A good initiative to know about Automation feedback.
Seems,  calendly schedule is about in AM timeline, will drop notes here.

- Major:
A view for automation run is shown for top few automation, but that this was part of many other runs, that's no where easy to find.

[Denise Lydia Ellis]

Hi Charlie, some requests below:

• As a Jira administrator, I want a failed/error automation rule to automatically create an incident/work item in a designated project and ability to assign it to the Jira admin team or rule owner, So that failures are tracked, triaged, and resolved promptly instead of relying only on email notifications to a email account.
• As a Org-, Site-, Jira admin, I want the system to warn me if I deactivate a user who is configured as the actor for any automation rules, So that I can prevent rules from failing due to lack of permissions once the user is inactive.
• As a Org-, Site-, Jira admin, I want Jira to warn me when I attempt to deactivate a user who owns one or more automation rules, So that I can review and reassign those rules before completing the deactivation and avoid unexpected rule failures or orphaned ownership.
• As a Org-, Site-, Jira admin, I want Jira to warn me if a user is configured as a recipient for automation failure notifications, So that I can redirect those alerts to an active mailbox or group and ensure failures are still monitored.
• As a Jira administrator, I want a consolidated impact panel when deactivating a user, So that I can see all automation-related dependencies in one place before confirming/committing deactivation.

[Piyush Annadate _ACE Pune_]

- Ticket about the failure is a good use case.
- If automation can have an event endpoint- would be good.