Issue Summary

The Jira Cloud audit log (Settings > System > Audit log) records sprint lifecycle events (Sprint Created, Sprint Started, Sprint Closed, Sprint Deleted) and displays the sprint name at the time the event occurred. However, the numeric Sprint ID is never displayed in the audit log UI, included in the CSV export, or exposed as a searchable/filterable field in the REST API (/rest/api/3/auditing/record).

This creates a significant gap for administrators who need to correlate audit log entries with a specific sprint — particularly when a sprint has been renamed after creation, or when multiple sprints share similar names. The only reliable unique identifier for a sprint is its numeric ID, but there is currently no way to search for or confirm it through any customer-facing audit log interface.

Steps to Reproduce

1. In Jira Cloud, go to Settings (gear icon) > System > Audit log.
2. Search for a sprint creation or deletion event (e.g., filter by category "sprints" or search by sprint name).
3. Expand the event details by clicking 'Show more' on any sprint-related entry.
4. Observe that the sprint's numeric ID is not displayed anywhere in the event details.
5. Export the audit log to CSV and open the file.
6. Observe that no column in the CSV export contains the sprint's numeric ID.
7. Call GET /rest/api/3/auditing/record?filter=<sprint name> — observe the record is found.
8. Call GET /rest/api/3/auditing/record?filter=<sprint ID> (e.g., filter=28176) — observe no results are returned, confirming that objectItem.id is not a searchable field.

Expected Results

• The sprint's numeric ID should be visible in the audit log UI when expanding a sprint event's details.
• The sprint's numeric ID should be included as a column in the CSV export.
• The REST API filter parameter should support matching against objectItem.id, allowing administrators to query audit records directly by Sprint ID.

Actual Results

• The audit log UI displays only the sprint name (as it was at the time of the event), with no numeric Sprint ID shown.
• The CSV export contains no column for the sprint's numeric ID.
• The REST API filter parameter does not search objectItem.id, so passing a numeric Sprint ID (e.g., 28176) returns no results.
• If a sprint is renamed after creation, the audit log entry retains the original name, making it difficult to correlate the entry with the sprint's current state without backend database access.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.