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:
A JQL expression. For performance reasons, this parameter requires a bounded query. A bounded query is a query with a search restriction.
order by key desc
.assignee = currentUser() order by key
.Additionally, orderBy
clause can contain a maximum of 7 fields.
The token for a page to fetch that is not the first page. The first page has a nextPageToken
of null
. Use the nextPageToken
to fetch the next page of issues.
Note: The nextPageToken
field is not included in the response for the last page, indicating there is no next page.
id
or key
only. It returns max 5000 issues.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.id
Returns only issue IDs.The default is id
.
Examples:
summary,comment
Returns only the summary and comments fields only.-description
Returns all navigable (default) fields except description.*all,-comment
Returns all fields except comments.Multiple fields
parameters can be included in a request.
Note: By default, this resource returns IDs only. This differs from GET issue where the default is all fields.
Use expand to include additional information about issues in the response. Note that, unlike the majority of instances where expand
is specified, expand
is defined as a comma-delimited string of values. The expand options are:
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 fields
, returns versionedRepresentations
a JSON array containing each version of a field's value, with the highest numbered item representing the most recent version.Examples: "names,changelog"
Returns the display name of each field as well as a list of recent updates to an issue.
false
.Specify how the response should be mapped to the table output. The following formats are available:
Structured Table: Returns a parsed table with data split into rows and columns.
Raw Response: Returns the raw response in a single row with the following columns:
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.
To use this node in KNIME, install the extension Jira Nodes from the below update site following our NodePit Product and Node Installation Guide:
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 mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.