Sprint Start Date entry in Jira Audit log does not match with the Actual Sprint Date

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

Sprint Start Date entry in Jira Audit log does not match with the Actual Sprint Date

Environment

Jira Cloud

Cause

When a sprint is started an entry in the Jira Audit log gets logged similar to below

(Auto-migrated image: description temporarily unavailable)

The date that get logged in the Audit log is the system time as per Default user time zone and not the actual sprint start date. It is quite possible that when starting a sprint we give previous dates and audit log does not capture that. For the actual sprint start date always refer the sprint reports.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.