GET /rest/api/2/priority/search
Returns a paginated list of priorities. The list can contain all priorities or a subset determined by any combination of these criteria:
- a list of priority IDs. Any invalid priority IDs are ignored.
- a list of project IDs. Only priorities that are available in these projects will be returned. Any invalid project IDs are ignored.
- whether the field configuration is a default. This returns priorities from company-managed (classic) projects only, as there is no concept of default priorities in team-managed projects.
Deprecation notice: The onlyDefault parameter is deprecated and will be removed at a later date. See CHANGE-1655.
Deprecation notice: The isDefault property of priorities is deprecated and will be removed at a later date. See CHANGE-1655.
Permissions required: Permission to access Jira.
Servers
- https://your-domain.atlassian.net
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
id[] |
Array | No |
The list of priority IDs. To include multiple IDs, provide an ampersand-separated list. For example, |
projectId[] |
Array | No |
The list of projects IDs. To include multiple IDs, provide an ampersand-separated list. For example, |
startAt |
String | No |
The index of the first item to return in a page of results (page offset). Default value: "0" |
maxResults |
String | No |
The maximum number of items to return per page. Default value: "50" |
expand |
String | No |
Use |
priorityName |
String | No |
The name of priority to search for. |
onlyDefault |
Boolean | No |
Whether only the default priority is returned. Default value: false |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.