Provide an estimated count of the issues that match the JQL. Recent updates might not be immediately visible in the returned output. This endpoint requires JQL to be bounded.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has:
Optionalcallback: undefinedReturns lists of issues matching a query string. Use this resource to provide auto-completion suggestions when the user is looking for an issue using a word or string.
This operation returns two lists:
History Search which includes issues from the user's history of created, edited, or viewed issues that contain
the string in the query parameter.Current Search which includes issues that match the JQL expression in currentJQL and contain the string in the
query parameter.This operation can be accessed anonymously.
Permissions required: None.
Returns lists of issues matching a query string. Use this resource to provide auto-completion suggestions when the user is looking for an issue using a word or string.
This operation returns two lists:
History Search which includes issues from the user's history of created, edited, or viewed issues that contain
the string in the query parameter.Current Search which includes issues that match the JQL expression in currentJQL and contain the string in the
query parameter.This operation can be accessed anonymously.
Permissions required: None.
Optionalparameters: Version2Parameters.GetIssuePickerResourceOptionalcallback: undefinedChecks whether one or more issues would be returned by one or more JQL queries.
Permissions required: None, however, issues are only matched against JQL queries where the user has:
Checks whether one or more issues would be returned by one or more JQL queries.
Permissions required: None, however, issues are only matched against JQL queries where the user has:
Optionalcallback: undefinedSearches for IDs of issues using JQL.
Use the Search endpoint if you need to fetch more than just issue IDs. The Search endpoint returns more information, but may take much longer to respond to requests. This is because it uses a different mechanism for ordering results than this endpoint and doesn't provide the total number of results for your query.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has:
Searches for IDs of issues using JQL.
Use the Search endpoint if you need to fetch more than just issue IDs. The Search endpoint returns more information, but may take much longer to respond to requests. This is because it uses a different mechanism for ordering results than this endpoint and doesn't provide the total number of results for your query.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has:
Optionalcallback: undefinedSearches for issues using JQL.
If the JQL query expression is too large to be encoded as a query parameter, use the POST version of this resource.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has:
Searches for issues using JQL.
If the JQL query expression is too large to be encoded as a query parameter, use the POST version of this resource.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has:
Optionalcallback: undefinedSearches for issues using JQL. Recent updates might not be immediately
visible in the returned search results. If you need
read-after-write consistency, you can
utilize the reconcileIssues parameter to ensure stronger consistency assurances. This operation can be accessed
anonymously.
If the JQL query expression is too large to be encoded as a query parameter, use the POST version of this resource.
Permissions required: Issues are included in the response where the user has:
Searches for issues using JQL. Recent updates might not be immediately
visible in the returned search results. If you need
read-after-write consistency, you can
utilize the reconcileIssues parameter to ensure stronger consistency assurances. This operation can be accessed
anonymously.
If the JQL query expression is too large to be encoded as a query parameter, use the POST version of this resource.
Permissions required: Issues are included in the response where the user has:
Optionalcallback: undefinedSearches for issues using JQL. Recent updates might not be immediately
visible in the returned search results. If you need
read-after-write consistency, you can
utilize the reconcileIssues parameter to ensure stronger consistency assurances. This operation can be accessed
anonymously.
Permissions required: Issues are included in the response where the user has:
Searches for issues using JQL. Recent updates might not be immediately
visible in the returned search results. If you need
read-after-write consistency, you can
utilize the reconcileIssues parameter to ensure stronger consistency assurances. This operation can be accessed
anonymously.
Permissions required: Issues are included in the response where the user has:
Optionalcallback: undefinedSearches for issues using JQL.
There is a GET version of this resource that can be used for smaller JQL query expressions.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has:
Searches for issues using JQL.
There is a GET version of this resource that can be used for smaller JQL query expressions.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has:
Optionalparameters: Version2Parameters.SearchForIssuesUsingJqlPostOptionalcallback: undefined
Provide an estimated count of the issues that match the JQL. Recent updates might not be immediately visible in the returned output. This endpoint requires JQL to be bounded.
This operation can be accessed anonymously.
Permissions required: Issues are included in the response where the user has: