Get issue
Returns the details for an issue.
The issue is identified by its ID or key, however, if the identifier doesn't match an issue, a case-insensitive search and check for moved issues is performed. If a matching issue is found its details are returned, a 302 or other redirect is not returned. The issue key returned in the response is the key of the issue found.
This operation can be accessed anonymously.
Permissions required:
A list of fields to return for the issue. This parameter accepts a comma-separated list. Use it to retrieve a subset of fields. Allowed values:
*all
Returns all fields.*navigable
Returns navigable fields.Examples:
summary,comment
Returns only the summary and comments fields.-description
Returns all (default) fields except description.*navigable,-comment
Returns all navigable fields except comment.This parameter may be specified multiple times. For example, fields=field1,field2& fields=field3
.
Note: All fields are returned by default. This differs from Search for issues using JQL (GET) and Search for issues using JQL (POST) where the default is all navigable fields.
fields
are referenced by keys rather than IDs. This parameter is useful where fields have been added by a connect app and a field's key may differ from its ID.Use expand to include additional information about the 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.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
Returns a JSON array for each version of a field's value, with the highest number representing the most recent version. Note: When included in the request, the fields
parameter is ignored.A list of issue properties to return for the issue. This parameter accepts a comma-separated list. Allowed values:
*all
Returns all issue properties.Examples:
*all
Returns all properties.*all,-prop1
Returns all properties except prop1
.prop1,prop2
Returns prop1
and prop2
properties.This parameter may be specified multiple times. For example, properties=prop1,prop2& properties=prop3
.
lastViewed
field.failFast=true
, if one field fails, the entire operation fails. For failFast=false
, the operation will continue even if a field fails. It will return a valid response, but without values for the failed field(s).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, 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.