Sprints

Manages Jira sprints. Supports creating, modifying, deleting, and querying sprint data from agile boards.

Table Specific Information

Select

To retrieve a list of Sprints in your Jira account, you can query the BoardSprints view.

The connector uses the Jira API to process some of the filters. The connector will process the rest of the filter client side within itself. For example, the following query is processed server-side:

SELECT * FROM Sprints WHERE Id = 122 
SELECT * FROM Sprints WHERE Id IN ('1', '2', '3')

INSERT

Create a new sprint and link it to a board. The OriginBoardId and the Name columns are required for inserting a new sprint.

INSERT INTO Sprints (OriginBoardId, Name, Goal, StartDate, EndDate) VALUES ('1', 'Inserted Sprint', 'Complete target', '2018-02-02', '2018-04-04')

Update

Make changes to a sprint by specifying the sprint's Id.

UPDATE Sprints SET State = 'active' WHERE Id = 305

Delete

Remove a sprint by specifying the Id.

DELETE FROM Sprints WHERE Id = 305

Columns


Name	Type	ReadOnly	References	SupportedOperators	Platform	Description
Id [KEY]	Integer	True		=,IN	Common	A unique numeric identifier assigned to the sprint. Used internally to reference the sprint in Jira and API calls.
Name	String	False			Common	The name given to the sprint, typically reflecting its time frame or theme. Helps teams identify and organize sprints easily.
State	String	False		=	Common	The current state of the sprint. Valid states include 'future' (not started), 'active' (in progress), and 'closed' (completed). States transition in this strict order. The allowed values are future, active, closed.
Goal	String	False			Common	A short statement describing the objective of the sprint. Helps align the team on what the sprint is intended to achieve.
OriginBoardId	Integer	False	Boards.Id		Common	The ID of the agile board from which the sprint was created. This value is set at creation and cannot be changed.
StartDate	Datetime	False			Common	The date and time when the sprint was officially started. Typically marks the beginning of the development cycle.
EndDate	Datetime	False			Common	The planned date and time when the sprint is expected to end. This can be used to calculate sprint duration and track timelines.
CompleteDate	Datetime	True			Common	The actual date and time when the sprint was marked as completed in Jira. Useful for reporting and retrospective analysis.