-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Administration - Audit Log
-
None
-
1
-
Severity 3 - Minor
Issue Summary
Jira Cloud audit log export confirmation shows total available events instead of filtered event count
Steps to Reproduce
- Log in to Jira Cloud as a user with access to the audit log.
- Go to Administration → System → Audit log.
- Confirm that the audit log shows a large number of events (e.g. 1,000 events in “Available history”).
- Apply filters so that the list is narrowed down, for example:
- Set a Date/Period filter to a recent time range, and/or
- Filter by Category / Summary / User so that only a subset of entries is shown (e.g. around 100 events).
- Click Export (CSV or JSON) for the audit log.
Expected Results
The export confirmation should accurately reflect what will be exported. For example:
Actual Results
When the export file is downloaded and opened:
- The file actually contains only the filtered events (~100),
- Not all 1,000 events from the full available history.
So the UI text is misleading: it suggests that the export will include all events from the full audit log history, but in reality the export correctly respects the filters and only includes the filtered subset.
Workaround
- The export itself works correctly and respects the current filters; only the wording in the confirmation dialog is incorrect.
- Admins can:
- Check the filtered count in the UI before exporting, and
- Confirm that the number of rows in the exported file matches the filtered view (rather than the “available history” count shown in the dialog).