Module issue_search_api

Source

Enums§

GetIssuePickerResourceError
struct for typed errors of method get_issue_picker_resource
MatchIssuesError
struct for typed errors of method match_issues
SearchForIssuesUsingJqlError
struct for typed errors of method search_for_issues_using_jql
SearchForIssuesUsingJqlPostError
struct for typed errors of method search_for_issues_using_jql_post

Functions§

get_issue_picker_resource
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.
match_issues
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: * Browse projects project permission for the project that the issue is in. * If issue-level security is configured, issue-level security permission to view the issue.
search_for_issues_using_jql
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: * Browse projects project permission for the project containing the issue. * If issue-level security is configured, issue-level security permission to view the issue.
search_for_issues_using_jql_post
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: * Browse projects project permission for the project containing the issue. * If issue-level security is configured, issue-level security permission to view the issue.