--- title: "Data Source - JIRA" slug: "data-source-jira" updated: 2024-09-19T08:13:55Z published: 2024-09-19T08:13:55Z canonical: "documents.trocco.io/data-source-jira" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.trocco.io/llms.txt > Use this file to discover all available pages before exploring further. # Data Source - JIRA ## summary Help page for ETL Configuration of Data Settings for JIRA Software. ## constraints - none in particular ## Setting items ### STEP1 Basic settings | item name | indispensable | default value | Description. | | --- | --- | --- | --- | | JIRA Connection Configuration | Yes | - | Select the preregistered [JIRA Connection](/docs/connection-configuration-jira) Configuration that has the necessary permissions for this ETL Configuration. | | JQL | Yes | - | Enter the [Jira Query Language (JQL) for](https://www.atlassian.com/ja/software/jira/guides/jql/overview) capturing issues. | | Expand | No | - | Additional columns can be specified. Please refer to [the official JIRA REST API documentation for](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get) possible values. | | Automatic expansion op-jons for JSON columns | Yes | not to be expanded | If you choose **to automatically expand JSON columns**, they will be expanded as follows Contents of original JSON column:. `{"id": 10, "person": {"age": 30}}`Expanded column names:. `(JSON_column_name).id, (JSON_column_name).person.age` Note that Data Destination cannot use periods ( `.` ) as column names `.` as a column name at the destination, an error will occur during transfer. If you want to configure the details of how JSON columns are expanded, please **also** use **the Column Setting in** ETL Configuration STEP 2. | #### STEP1 detailed settings Click on **Set Details** to display the configuration items. | item name | indispensable | default value | | --- | --- | --- | | Retry interval (sec) | Yes | 1 | | Maximum number of retries | Yes | 5 | | Maximum number of fetches per API request | Yes | 50 |