Jira

Jira Cloud is a work-management platform used to track issues, projects, releases, and service requests through Atlassian REST APIs.

The Flowgear Jira Node lets a Workflow query and modify Jira Cloud resources by using an OAuth Connection and template-selected operations.

Revision History

0.0.0.16 - Preserved inherited fields in designer templates when OpenAPI schemas use constraints-only allOf overlays.
0.0.0.15 - Removed query paging controls from templates and kept paging inside the Node.
0.0.0.14 - Current release.

Connection

Use a Jira OAuth Connection for all methods.

Property	Type	Description
`Cloud ID`	String	Jira Cloud tenant ID. Click `Acquire Metadata` to populate it automatically when the Atlassian account has access to one site, or to list available IDs when it has access to multiple sites.
`Client ID`	String	Client ID from your Atlassian OAuth app.
`Client Secret`	Masked	Client secret from your Atlassian OAuth app.
`Access Token`	Masked	OAuth access token populated after you connect the account.
`Refresh Token`	Masked	OAuth refresh token used to renew the access token when it expires.
`Scope`	String	Space-delimited Atlassian scopes requested during authorization. The default value is `read:jira-work offline_access`.
`Timeout (seconds)`	Integer	Timeout applied to Jira API calls. The default value is `30`.

Setup Notes

Create an Atlassian OAuth 2.0 app for Jira Cloud and use its Client ID and Client Secret in the Connection.
Authorize the Connection so Flowgear can store Access Token and Refresh Token.
Click Acquire Metadata to populate Cloud ID when only one Jira site is available. If multiple sites are returned, select the correct Cloud ID from the list shown in the message.
Run the Connection test after Cloud ID is set to validate access.
The default Scope value is read:jira-work offline_access. Change it if the Jira operations you want to run need additional Atlassian scopes.
This Node is for Jira Cloud. Jira Server and Jira Data Center are not supported.

Methods

The Jira Node exposes four invoke methods that use template-selected OperationId values from the embedded Jira OpenAPI schema.

Query

Executes a Jira query operation and streams all result pages.

Parameter	Type	Description
`Connection`	Connection	The Jira OAuth `Connection`.
`OperationId`	String	Identifier of the Jira operation to execute. Templates set this value for the selected operation.
`Parameters`	Object	Optional route and query parameters required by the selected operation.

Return	Type	Description
`Response`	Array	One response row per returned Jira item. Successful results expose Jira fields at the row root. When Jira responds with `value`, `values`, or `issues`, the Node emits each contained item separately.

Create

Executes a Jira create operation and sends request body items to the selected endpoint.

Parameter	Type	Description
`Connection`	Connection	The Jira OAuth `Connection`.
`OperationId`	String	Identifier of the Jira operation to execute. Templates set this value for the selected operation.
`Parameters`	Object	Optional route and query parameters required by the selected operation.
`Items`	Array	Request body items for the selected create operation. One item sends one JSON object body. When the target operation supports array request bodies, multiple items are sent as one JSON array.

Return	Type	Description
`Response`	Array	One response row per Jira response item. Successful rows include returned Jira fields and can include `input` so you can match the response to the submitted item.

Update

Executes a Jira update operation and sends request body items to the selected endpoint.

Parameter	Type	Description
`Connection`	Connection	The Jira OAuth `Connection`.
`OperationId`	String	Identifier of the Jira operation to execute. Templates set this value for the selected operation.
`Parameters`	Object	Optional route and query parameters required by the selected operation.
`Items`	Array	Request body items for the selected update operation. One item sends one JSON object body. When the target operation supports array request bodies, multiple items are sent as one JSON array.

Return	Type	Description
`Response`	Array	One response row per Jira response item. Successful rows include returned Jira fields and can include `input` so you can match the response to the submitted item.

Delete

Executes a Jira delete operation.

Parameter	Type	Description
`Connection`	Connection	The Jira OAuth `Connection`.
`OperationId`	String	Identifier of the Jira operation to execute. Templates set this value for the selected operation.
`Parameters`	Object	Optional route and query parameters required by the selected operation.

Return	Type	Description
`Response`	Array	One response row for the delete result. Successful rows include any Jira response fields returned by the endpoint.

Usage Notes

Use templates to pick supported Jira operations. The built-in Get Available Cloud IDs query template lists the Jira sites that the current OAuth account can access.
Query templates omit startAt, maxResult, and maxResults. The Node determines the provider page size and follows Jira pages internally.
Successful Query rows do not add Flowgear success metadata, so downstream Steps receive the Jira payload fields directly.
When Create or Update sends individual Items, the response can include an input field so you can match each result to the submitted payload.

Known Issues

Query template return schemas are generated from the upstream OpenAPI sampler, so some templates can describe Jira's envelope shape more broadly than the flattened runtime output.