Determining Sprint Status from the Database
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Purpose
Sprint states (Active, Completed, Future) aren't stored directly in the database. Read on for a method to calculate the state based on the values of two columns in the AO_60DB71_SPRINT table.
Solution
- You can determine the sprint status by evaluating the values of the CLOSED and STARTED columns of the AO_60DB71_SPRINT table.
- When STARTED is t and CLOSED is f, that's indicative of an active sprint
- When CLOSED is t, that's indicative of a completed sprint
When STARTED is f, that's indicative of a future sprint
As a practical example:
select * from "AO_60DB71_SPRINT"; CLOSED | COMPLETE_DATE | END_DATE | GOAL | ID | NAME | RAPID_VIEW_ID | SEQUENCE | STARTED | START_DATE --------+---------------+---------------+------+----+-----------------+---------------+----------+---------+--------------- f | | 1532407100657 | | 1 | Sample Sprint 2 | 1 | | t | 1531196300657 t | 1531187301433 | 1531192101433 | | 2 | Sample Sprint 1 | 1 | | t | 1529982501433 f | | | | 3 | Sample Sprint 3 | 1 | | f | (3 rows)
Using the criteria outlined above, Sample Sprint 1 is a completed sprint, Sample Sprint 2 is an active sprint, and Sample Sprint 3 is a future sprint.