Skip to main content Skip to complementary content
Qlik Resources
Announcements
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

tJIRAOutput

Inserts, updates, or deletes the issue or project information in JIRA.

tJIRAOutput Standard properties

These properties are used to configure tJIRAOutput running in the Standard Job framework.

The Standard tJIRAOutput component belongs to the Business family.

The component in this framework is available in all Talend products.

Basic settings

Properties Description

Property Type

Select the way the connection details will be set.

  • Built-In: The connection details will be set locally for this component. You need to specify the values for all related connection properties manually.

  • Repository: The connection details stored centrally in Repository > Metadata will be reused by this component.

    You need to click the [...] button next to it and in the pop-up Repository Content dialog box, select the connection details to be reused, and all related connection properties will be automatically filled in.

This property is not available when other connection component is selected from the Connection Component dropdown list.
Schema and Edit schema

A schema is a row description that defines the number of fields (columns) to be processed and passed on to the next component.

Note that the schema of this component is empty by default and you need to click Edit schema to manually set it depending on your needs:
  • If you selected Insert in the Output Action list, add a single column json of String type.
  • If you selected Update in the Output Action list, add two columns id and json of String type.
  • If you selected Delete in the Output Action list, add a single column id of String type.

Jira version

Select one of the following Jira API versions:
  • Jira Server (v2) is Jira on-premises and uses the REST API v2.
  • Jira Cloud (v3) is Jira Cloud and uses the REST API v3.
    Cloud-specific considerations:

    • Rate limits: Jira Cloud may return HTTP 429 (Too Many Requests) responses when API rate limits are exceeded. Your integration should detect these responses and implement retry logic with exponential backoff, respecting any Retry-After header provided.

    • JQL limits: Jira Cloud enforces a JQL length limit (~5000 characters). Only GET requests are supported for queries approaching this limit.

    • Permissions and scopes: Access depends on Jira Cloud permissions. Missing permissions can cause authentication or authorization failures.

    • Validation errors: When using Jira Cloud v3, request bodies must be constructed according to the Atlassian Document Format (ADF) schema. Payloads compatible with v2 will not work as-is with v3; make sure that JSON payloads, including ADF content, match the expected structure and field requirements. Otherwise, Jira will return validation errors for malformed or incorrectly formatted requests.
    • The Jira API is asynchronous, so tJiraOutput may confirm success before the ticket is actually created. If your Job requires the ticket immediately, allow for a delay before it appears in Jira.
Authentication options

Select one of the following authentication methods depending on the server version and security requirements:

  • If you selected Jira Server (v2):

    • Basic: Specify the username and password to access JIRA.

      To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

    • Personal Access Token: To enter the JIRA personal access token, click the [...] button next to the Token field, paste the token, and click OK to save the settings.
  • If you selected Jira Cloud (v3):

    • Email and Token: Specify the email address to access JIRA, as well as the JIRA API token. Click the [...] button next to the Token field, paste the token, and click OK to save the settings.
User Id and Password

Specify the user authentication data used to access JIRA.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.
Resource type

Select the JIRA resource from the drop-down list, either Issue or Project.
Output action Select an operation to be performed from the drop-down list.

  • Create: create new issue or project information into JIRA.

  • Update: modify existing issue or project information in JIRA.

  • Delete: remove issue or project data in JIRA corresponding to the input flow.

Advanced settings

Properties Description
Delete subtasks Select this check box to delete the subtask(s).

This check box is available only when ISSUE is selected from the JIRA resource drop-down list and Delete is selected from the Output Action drop-down list.
tStatCatcher Statistics

Select this checkbox to gather the Job processing metadata at the Job level as well as at each component level.

Global Variables

Variables Description
Global Variables

NB_LINE: the number of rows processed. This is an After variable and it returns an integer.

NB_SUCCESS: the number of rows successfully processed. This is an After variable and it returns an integer.

NB_REJECT: the number of rows rejected. This is an After variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error checkbox is cleared, if the component has this checkbox.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

Usage

Usage guidance Description
Usage rule

This component is usually used as an end component of a Job or subJob and it always needs an input link.
Related concepts

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here