Skip to main content Skip to complementary content

Retrieving the new issue information from JIRA application

Procedure

  1. Double-click the tJIRAInput component to open its Basic settings view.
  2. Select Issue from the JIRA resource drop-down list.
  3. In the JQL field, enter the JQL query used to retrieve issues in JIRA application.
    In this example, the query is project = DOC ORDER BY created DESC. All issues under the project DOC will be retrieved and they will be sorted by the creation date in descending order.
  4. Double-click the tExtracJSONFields component to open its Basic settings view.
  5. Click the [...] button next to Edit schema, and in the schema dialog box displayed, define the schema by adding five columns of String type, id, key, project, description, and summary, which will hold the corresponding information of each issue retrieved.

    When done, click OK to save the changes and close the dialog box.

  6. 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.
  7. 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.
  8. 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, $.fields.project.key for the project column, $.fields.description for the description column, and $.fields.summary for the summary column.
  9. Double-click the tFileOutputJSON component to open its Basic settings view.
  10. In the File Name field, specify the path to the file into which the extracted issue information will be written, D:/JiraComponents/issue_info.json in this example. And in the Name of data block field, enter the name of the data block, issue 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 – let us know how we can improve!

Leave your feedback here