Jira
Connect Jira to sanda: what to prepare, the fields the connection form asks for, and how its data lands in your warehouse.
Connect Jira
- Open the catalogue. In the console, go to Data · Connections and press New connection.
- Choose Jira. It is listed under product and operations; you can also search for it by name.
- Fill in the form. Enter the fields below. Credentials go straight to sanda’s sync engine and are never stored in sanda’s database.
- Choose what to sync. Pick the streams you want, and a sync mode for each. See choose what to sync.
- Run the first sync. sanda tests the connection, then lands each stream as a table in your warehouse.
Configuration fields
What the connection form asks for. Required fields are marked; the rest are optional.
| Field | Type | Required | Description |
|---|---|---|---|
| Authentication | one of 3 options | Yes | Choose how to authenticate to Jira. |
| Domain | string | Yes | Your Jira host (full domain: do not include 'https://' or paths). Examples: your-domain.atlassian.net, your-domain.jira.com, jira.your-domain.com. |
| Projects | array | No | List of Jira project keys to replicate data for, or leave it empty if you want to replicate data for all projects. |
| Start Date | string | No | The date from which you want to replicate data from Jira, use the format YYYY-MM-DDT00:00:00Z. Note that this field only applies to certain streams, and only data generated on or after the start date will be replicated. Or leave it empty if you want to replicate all data. |
| Lookback window | integer | No | When set to N, the connector will always refresh resources created within the past N minutes. By default, updated objects that are not newly created are not incrementally synced. Default 0. |
| Number of concurrent threads | integer | No | The number of worker threads to use for the sync. Default 5. |
Authentication
Choose how to authenticate to Jira.
Choose one of the following. Each asks for its own fields.
API Token
| Field | Type | Required | Description |
|---|---|---|---|
| string | Yes | The user email for your Jira account which you used to generate the API token. This field is used for Authorization to your account by BasicAuth. | |
| API Token | string, secret | Yes | Jira API Token. API Token is used for Authorization to your account by BasicAuth. |
Service Account
| Field | Type | Required | Description |
|---|---|---|---|
| Service Account Token | string, secret | Yes | Atlassian Service Account API token. Service account API tokens authenticate with Bearer authentication and use Atlassian's Platform API Gateway. |
OAuth2.0
| Field | Type | Required | Description |
|---|---|---|---|
| Client ID | string, secret | Yes | The Client ID of your Atlassian OAuth application. |
| Client Secret | string, secret | Yes | The Client Secret of your Atlassian OAuth application. |
| Refresh Token | string, secret | Yes | The Refresh Token obtained after completing the OAuth flow. |
Related
Something unclear or out of date? Tell us, and we will fix the page.