Search for issues using JQL (GET)
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:
The JQL that defines the search. Note:
userkey cannot be used as search terms due to privacy reasons. Use
The maximum number of items to return per page. To manage page size, Jira may return fewer items per page where a large number of fields are requested. The greatest number of items returned per page is achieved when requesting
Determines how to validate the JQL query and treat the validation results. Supported values are:
strict Returns a 400 response code if any errors are found, along with a list of all errors (and warnings).
warn Returns all errors as warnings.
none No validation is performed.
true Deprecated A legacy synonym for
false Deprecated A legacy synonym for
Note: If the JQL is not correctly formed a 400 response code is returned, regardless of the
A list of fields to return for each issue, use it to retrieve a subset of fields. This parameter accepts a comma-separated list. Expand options include:
*all Returns all fields.
*navigable Returns navigable fields.
summary,comment Returns only the summary and comments fields.
-description Returns all navigable (default) fields except description.
*all,-comment Returns all fields except comments.
This parameter may be specified multiple times. For example,
Note: All navigable fields are returned by default. This differs from GET issue where the default is all fields.
Use expand to include additional information about issues in the response. This parameter accepts a comma-separated list. Expand options include:
renderedFields Returns field values rendered in HTML format.
names Returns the display name of each field.
schema Returns the schema describing a field type.
transitions Returns all possible transitions for the issue.
operations Returns all possible operations for the issue.
editmeta Returns information about how each field can be edited.
changelog Returns a list of recent updates to an issue, sorted by date, starting from the most recent.
versionedRepresentations Instead of
versionedRepresentations a JSON array containing each version of a field's value, with the highest numbered item representing the most recent version.
A list of issue property keys for issue properties to include in the results. This parameter accepts a comma-separated list. Multiple properties can also be provided using an ampersand separated list. For example,
properties=prop1,prop2&properties=prop3. A maximum of 5 issue property keys can be specified.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to email@example.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.