Sprint Dates for Jira

Documentation

Last updated: 22 September 2026

Sprint Dates for Jira adds two read-only date fields — Sprint Start Date and Sprint End Date — and keeps them in sync with each work item’s current sprint. You can search, sort, and export those dates in Issue Navigator and CSV, which is the gap tracked in JRACLOUD-72007.

Set up

  1. Open Jira admin → Work items → Screens and add both fields to the screens used by your Scrum projects.
  2. Open Apps → Sprint Dates and run a backfill so existing work items get dates.
  3. In Issue Navigator, add Sprint Start Date and Sprint End Date as columns. Try JQL such as "Sprint End Date" <= endOfWeek().

Which sprint is used?

If a work item is in an active sprint, those dates are used. Otherwise a future sprint is used. Closed sprints are kept as history only. If there is no current sprint, both fields are cleared. Future sprints with no dates stay empty until dates are set. Kanban work items without sprints stay empty.

When sprint dates change

When someone reschedules a sprint on the board, the app updates every work item in that sprint. Moving a work item between sprints also refreshes its fields. That is the usual gap in Automation workarounds that only copy dates once.

Why not Automation?

Automation can copy a sprint date into Due Date, but that overwrites Due Date, is often per-project, and usually does not run when someone reschedules the sprint. This app keeps dedicated fields and updates the whole sprint when dates change.

Subscription

After the Marketplace 30-day trial, a paid subscription is required to keep sprint dates updating. Existing field values are not cleared if the subscription lapses. Sites with up to 10 Jira users stay free under the listing price.

Security

The app runs on Atlassian Forge. Read and write stay inside your site. There is no external data egress. See the privacy policy for what is accessed and stored.

Support

Email [email protected]. This documentation is published at https://sprintdates.icevid.dev/docs.