Hola Vitalii,
I think the documentation is a little ahead of the administration experience here. Atlassian recommends regularly reviewing connections and monitoring how they’re used, but I couldn’t find a native Jira Cloud screen that gives a site admin a centralized inventory of every Automation connection, its credential owner, last use, and the flows that depend on it. The connection documentation also says connections are scoped to an individual flow and can’t be reused across different flows, which makes centralized review harder when you have hundreds of them.
@Marc -Devoteam-'s audit log suggestion is useful for detecting failures, but it doesn’t fully address the governance question you’re asking. The Automation audit log can show recent activity for all flows in Jira, and you can filter by date, flow, actions, triggers, and advanced steps. However, Atlassian retains those Automation logs for only 90 days, so a healthy connection used infrequently may never appear during a periodic review.
There is also an Automation performance view that provides admins with execution counts, durations, and outcomes for flows, plus a separate Usage screen for overall Automation consumption. Those are useful for identifying active, failing, or expensive flows, but they report at the flow level rather than providing a connection-level inventory.
So, for the specific requirement of answering “Which external connections exist, who owns their credentials, which flows use them, and when was each connection last exercised?”, I don’t see a complete native admin report today.
With hundreds of flows, I’d use the global Automation view to narrow the review rather than opening every audit log manually. Go to Jira settings > System > Automation, then use the Flows list to filter by the external actions you use and review the relevant flows and their connections. The global Audit log can then identify recent execution failures or inactivity. I’d also use clear flow labels and connection names so those integrations can be identified consistently during reviews.
I’d consider raising a feedback request with Atlassian for a centralized Connections inventory that shows connection name, application, credential owner, associated flow, status, and last-used timestamp. That would align much more closely with the monitoring recommendation in Atlassian’s own best-practices documentation than the current flow-by-flow administration model.
Thanks,
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.