POST

Create a future sprint

Creates a future sprint. Sprint name and origin board id are required. Start and end date are optional. Notes: The sprint name is trimmed. Only Jira administrators can create synced sprints.

Request

Request bodyapplication/json

The sprint to create.

autoStartStop

boolean

endDate

string

goal

string

incompleteIssuesDestinationId

integer

name

string

originBoardId

integer

startDate

string

synced

boolean

userProfileTimeZone

string

Responses

Returns the created sprint.

application/json

SprintBean
POST/agile/1.0/sprint
1 2 3 4 5 curl --request POST \ --url 'http://{baseurl}/rest/agile/1.0/sprint' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json'
PUT

Unmap sprints from being synced

Sets the Synced flag to false for all sprints in the provided list.

Request

Request bodyapplication/json

The sprints to unmap.

sprintIds

array<integer>

Responses

Empty response is returned if operation was successful.

PUT/agile/1.0/sprint/unmap
1 2 3 4 curl --request PUT \ --url 'http://{baseurl}/rest/agile/1.0/sprint/unmap' \ --user 'email@example.com:<api_token>' \ --header 'Content-Type: application/json'
PUT

Unmap all sprints from being synced

Sets the Synced flag to false for all sprints on this Jira instance. This operation is intended for cleanup only. It is highly destructive and not reversible. Use with caution.

Request

This request has no parameters.

Responses

Empty response is returned if operation was successful.

PUT/agile/1.0/sprint/unmap-all
1 2 3 curl --request PUT \ --url 'http://{baseurl}/rest/agile/1.0/sprint/unmap-all' \ --user 'email@example.com:<api_token>'
GET

Get sprint by id

Returns a single sprint, for a given sprint Id. The sprint will only be returned if the user can view the board that the sprint was created on, or view at least one of the issues in the sprint.

Request

Path parameters

sprintId

integer

Required

Responses

Returns the requested sprint.

application/json

SprintBean
GET/agile/1.0/sprint/{sprintId}
1 2 3 4 curl --request GET \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json'
PUT

Update a sprint fully

Performs a full update of a sprint. A full update means that the result will be exactly the same as the request body. Any fields not present in the request JSON will be set to null. Notes:

  • Sprints that are in a closed state cannot be updated.
  • A sprint can be started by updating the state to 'active'. This requires the sprint to be in the 'future' state and have a startDate and endDate set.
  • A sprint can be completed by updating the state to 'closed'. This action requires the sprint to be in the 'active' state. This sets the completeDate to the time of the request. If the sprint has offending issues (those which are complete, but have incomplete subtasks) it cannot be closed. If issues are moved to new sprint user has to have issues edit permissions.
  • Other changes to state are not allowed.
  • The completeDate field cannot be updated manually.
  • Only Jira administrators can edit dates on sprints that are marked as synced.

Request

Path parameters

sprintId

integer

Required

Request bodyapplication/json

The updated sprint.

activatedDate

string

autoStartStop

boolean

completeDate

string

endDate

string

goal

string

id

integer

incompleteIssuesDestinationId

integer

name

string

originBoardId

integer

self

string

Responses

Returns the updated sprint.

application/json

SprintBean
PUT/agile/1.0/sprint/{sprintId}
1 2 3 4 5 curl --request PUT \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json'
POST

Partially update a sprint

Performs a partial update of a sprint. A partial update means that fields not present in the request JSON will not be updated. Notes:

  • Sprints that are in a closed state cannot be updated.
  • A sprint can be started by updating the state to 'active'. This requires the sprint to be in the 'future' state and have a startDate and endDate set.
  • A sprint can be completed by updating the state to 'closed'. This action requires the sprint to be in the 'active' state. This sets the completeDate to the time of the request. If the sprint has offending issues (those which are complete, but have incomplete subtasks) it cannot be closed. If issues are moved to new sprint user has to have issues edit permissions.
  • Other changes to state are not allowed.
  • The completeDate field cannot be updated manually.
  • Sprint goal can be removed by updating it's value to empty string
  • Only Jira administrators can edit dates on sprints that are marked as synced.

Request

Path parameters

sprintId

integer

Required

Request bodyapplication/json

The updated sprint.

activatedDate

string

autoStartStop

boolean

completeDate

string

endDate

string

goal

string

id

integer

incompleteIssuesDestinationId

integer

name

string

originBoardId

integer

self

string

Responses

Returns the updated sprint.

application/json

SprintBean
POST/agile/1.0/sprint/{sprintId}
1 2 3 4 5 curl --request POST \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json'
DEL

Delete a sprint

Deletes a sprint. Once a sprint is deleted, all issues in the sprint will be moved to the backlog. To delete a synced sprint, you must unsync it first.

Request

Path parameters

sprintId

integer

Required

Responses

Returned if the sprint was deleted successfully.

DEL/agile/1.0/sprint/{sprintId}
1 2 3 curl --request DELETE \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}' \ --user 'email@example.com:<api_token>'
GET

Get all issues in a sprint

Returns all issues in a sprint, for a given sprint Id. This only includes issues that the user has permission to view. By default, the returned issues are ordered by rank.

Request

Path parameters

sprintId

integer

Required

Query parameters

expand

string

jql

string

maxResults

integer

validateQuery

boolean

fields

array<StringList>

startAt

integer

Responses

Returns the requested issues, at the specified page of the results.

application/json

SearchResultsBean
GET/agile/1.0/sprint/{sprintId}/issue
1 2 3 4 curl --request GET \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}/issue' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json'
POST

Move issues to a sprint

Moves issues to a sprint, for a given sprint Id. Issues can only be moved to open or active sprints. The maximum number of issues that can be moved in one operation is 50.

Request

Path parameters

sprintId

integer

Required

Request bodyapplication/json

The issues to move.

issues

array<string>

Responses

Empty response is returned if operation was successful.

POST/agile/1.0/sprint/{sprintId}/issue
1 2 3 4 curl --request POST \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}/issue' \ --user 'email@example.com:<api_token>' \ --header 'Content-Type: application/json'
GET

Get all properties keys for a sprint

Returns the keys of all properties for the sprint identified by the id. The user who retrieves the property keys is required to have permissions to view the sprint.

Request

Path parameters

sprintId

string

Required

Responses

Returns the requested property keys.

application/json

EntityPropertiesKeysBean
GET/agile/1.0/sprint/{sprintId}/properties
1 2 3 4 curl --request GET \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}/properties' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json'
GET

Get a property for a sprint

Returns the value of the property with a given key from the sprint identified by the provided id. The user who retrieves the property is required to have permissions to view the sprint.

Request

Path parameters

propertyKey

string

Required
sprintId

string

Required

Responses

Returns the requested property.

application/json

EntityPropertyBean
GET/agile/1.0/sprint/{sprintId}/properties/{propertyKey}
1 2 3 4 curl --request GET \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}/properties/{propertyKey}' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json'
PUT

Update a sprint's property

Sets the value of the specified sprint's property. You can use this resource to store a custom data against the sprint identified by the id. The user who stores the data is required to have permissions to modify the sprint.

Request

Path parameters

propertyKey

string

Required
sprintId

string

Required

Responses

Returned if the sprint property is successfully updated.

PUT/agile/1.0/sprint/{sprintId}/properties/{propertyKey}
1 2 3 curl --request PUT \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}/properties/{propertyKey}' \ --user 'email@example.com:<api_token>'
DEL

Delete a sprint's property

Removes the property from the sprint identified by the id. Ths user removing the property is required to have permissions to modify the sprint.

Request

Path parameters

propertyKey

string

Required
sprintId

string

Required

Responses

Returned if the sprint property was removed successfully.

DEL/agile/1.0/sprint/{sprintId}/properties/{propertyKey}
1 2 3 curl --request DELETE \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}/properties/{propertyKey}' \ --user 'email@example.com:<api_token>'
POST

Swap the position of two sprints

Swap the position of the sprint with the second sprint.

Request

Path parameters

sprintId

integer

Required

Request bodyapplication/json

The sprint to swap with.

sprintToSwapWith

integer

swap

integer

Responses

Returned if the sprint swap was performed successfully.

POST/agile/1.0/sprint/{sprintId}/swap
1 2 3 4 curl --request POST \ --url 'http://{baseurl}/rest/agile/1.0/sprint/{sprintId}/swap' \ --user 'email@example.com:<api_token>' \ --header 'Content-Type: application/json'

Rate this page: