You cannot view a built-in activity log for individual Jira queries (JQL searches) in Jira Cloud or Data Center. However, you can reconstruct query activity using audit logs, issue history, and add-ons that log search events.
What Jira Actually Logs
Jira’s native logging focuses on changes to issues, not on the searches you run. The audit log (available in Jira Cloud and Data Center) records administrative actions such as permission changes, user creation, and project configuration. It does not record every JQL query typed into the search bar.
Issue history (the “History” tab on an issue) shows changes to fields, statuses, and comments. If a user runs a query and then edits an issue, that edit is logged, but the search that led to it is not.
Why Jira Doesn’t Log Queries by Default
Jira treats search queries as ephemeral. Logging every keystroke would create massive amounts of data, slow down performance, and raise privacy concerns. The platform assumes searches are transient and not worth persisting. This is a common frustration for admins who want to audit who searched for what, especially for compliance or troubleshooting.
How to See Query Activity with Add-Ons
If you need to track JQL queries, you must use a marketplace app. Popular options include Search Logger, Audit for Jira, and Insight (though the latter is more about assets). These apps typically:
- Record the JQL string, user, timestamp, and result count.
- Store logs in a separate table or export them to CSV.
- Provide dashboards to spot frequent or failed searches.
Before installing, check the app’s compatibility with your Jira version and its data retention policy. Some apps store logs for a limited time unless you pay for extended storage.
Using Jira’s Audit Log for Search-Related Events
While the audit log doesn’t capture queries, it does capture events that often accompany search activity, such as:
- Exporting issues (e.g., CSV export from a search).
- Creating a filter or updating a filter.
- Sharing a filter with a group or project.
- Deleting a filter.
To access the audit log in Jira Cloud: go to Administration > System > Audit log. In Data Center, it’s under Administration > Applications > Audit log. You can filter by user, date, and action type.
Common Misconception: “Recent Search History”
Many users confuse the “Recent” dropdown in the search bar with an activity log. That dropdown shows your recent searches, but only for your current browser session. It is not visible to admins and disappears when you clear your browser cache. It does not track other users’ queries.
Template: Query Logging Request Form
If you need to request query logging from your Jira admin, use this template. Fill in the blanks.
| Field | Details |
|---|---|
| Requester Name | _________________________ |
| Team/Project | _________________________ |
| Date of Request | _________________________ |
| Why do you need query logs? | _________________________ |
| What time period? | _________________________ |
| Which users or groups? | _________________________ |
| Approved by (admin) | _________________________ |
Sample (fictional): Requester Name: Jane Doe; Team: QA; Date: 2024-11-05; Why: To debug a failing filter; Time period: Last 30 days; Users: QA team; Approved by: John Smith.
Alternatives to Query Logging
If you cannot install an add-on, you can approximate query activity:
- Check filter usage in Jira’s “Popular filters” (though this only shows how often a filter is run, not who ran it).
- Enable Jira’s “Search request” logging in Data Center by setting the log level for
com.atlassian.jira.web.action.util.SearchRequestto DEBUG. This logs filter requests but not ad-hoc JQL. - Use database queries against the
searchrequesttable, but this only shows saved filters, not live searches.
Privacy and Security Considerations
Logging queries can expose sensitive data—users may search for issue keys containing confidential information. If you implement query logging, ensure you comply with your organization’s data protection policies. Restrict access to logs to admins only, and consider anonymizing usernames if you don’t need them. Also be aware that some add-ons store logs in the cloud, which may raise data residency concerns.
Frequently Asked Questions
Can I see who ran a specific JQL query in Jira?
Not by default. You would need an add-on that logs queries. Without one, you can only see saved filters and their last run time (if you have admin access to the filter’s permissions).
Does Jira Cloud store search history?
Jira Cloud stores your personal “Recent” searches in your browser’s local storage, but it does not store them on the server for admin review. Clearing your browser cache removes them.
How do I enable audit logging for searches in Jira?
You cannot enable audit logging for searches through native settings. You must install a third-party app that supports query logging. The audit log you can enable only covers administrative actions.
Is there a way to log JQL queries in Jira Data Center?
Yes, you can set the log level for com.atlassian.jira.web.action.util.SearchRequest to DEBUG in the logging settings. This will log filter requests, but not every ad-hoc search. For full query logging, use a marketplace add-on.
Can I export the audit log to see query activity?
Yes, you can export the audit log to CSV or JSON in Jira Cloud and Data Center. However, it will not contain query strings unless you have an add-on that writes them to the audit log.