Configuring the Job for retrieving the project information from JIRA application
Procedure
Double-click the tJIRAInput component to open its
Basic settings view.
In the Host URL, User Id, and
Password fields, specify the user authentication
information required to access the JIRA application.
Select Project from the JIRA
resource drop-down list, in the Project
ID field displayed, enter the key of the project, whose
information will be retrieved. In this example, it is
DOC.
Double-click the tExtractJSONFields component to open
its Basic settings view.
Click the [...] button next to Edit
schema, and in the schema dialog box displayed, define the
schema by adding six columns of String type, id,
key, name,
description, assigneeType, and
ProjectTypeKey, which will hold the corresponding
information of the specified project.
When done, click OK to save the changes and close the
dialog box.
Select the JSON field to be extracted from the JSON
field drop-down list. In this example, it is
json, which is passed from the
tJIRAInput component.
In the Loop Jsonpath query field, specify the path to
the node on which the loop is based. In this example, it is
$, which is the root node of the JSON field.
In the Mapping table, the Column
cells are automatically filled with the schema columns, and you need to specify
the corresponding JSON node that holds the desired data for each schema column.
In this example, $.id for the id
column, $.key for the key column,
$.name for the name column,
$.description for the
description column,
$.assigneeType for the
assigneeType column, and
$.projectTypeKey for the
projectTypeKey column.
Double-click the tFileOutputJSON component to open its
Basic settings view.
In the File Name field, specify the path to the file
into which the extracted project information will be written,
D:/JiraComponents/project_info.json in this example.
And in the Name of data block field, enter the name of
the data block, project in this example.
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!
