Jira Connector

Prerequisites

• A Jira Cloud instance (Atlassian Cloud)
• An Atlassian account with access to the Jira projects you want to sync

Getting Your Credentials

Jira Cloud uses Email + API Token authentication (Basic Auth).

Step 1: Find Your Jira Domain

Your Jira domain is visible in your browser URL when logged into Jira. For example: mycompany.atlassian.net.

Step 2: Create an API Token

1. Go to id.atlassian.com/manage-profile/security/api-tokens
2. Click Create API token
3. Enter a label (e.g., Landed sync)
4. Click Create
5. Copy the token

Important: The API token inherits the permissions of the Atlassian account that created it. The account must have access to the Jira projects you want to sync.

Configuration in Landed

Field	Value
Jira Domain	Your Atlassian Cloud domain (e.g., mycompany.atlassian.net)
Email	The email address of your Atlassian account
API Token	Your Atlassian API token

Available Streams

Stream	Description	Sync Mode
issues	Jira issues with summary, status, assignee, reporter, priority	Incremental
projects	Project definitions with key, name, type, lead	Full refresh
users	User records with display name, email, active status	Full refresh
sprints	Sprint records with state, dates, goals	Full refresh
boards	Agile board definitions (Scrum and Kanban)	Full refresh
worklogs	Time tracking work log entries	Incremental
issue_comments	Comments on issues	Incremental

Common Issues

Symptom	Cause	Fix
401 Unauthorized	Invalid email or API token	Verify your email and regenerate the API token
Domain format invalid	Domain not in .atlassian.net format	Use your Atlassian Cloud domain (e.g., mycompany.atlassian.net), not a custom domain
Missing issues	Account lacks project access	Ensure the Atlassian account has access to the relevant Jira projects
No sprints data	No Scrum boards configured	Sprints are only available for Scrum boards, not Kanban
Rate limit exceeded	Too many API calls	Landed handles rate limiting automatically

Data Notes

• Jira issues are fetched using JQL and sorted by updated date for incremental sync
• Custom fields are not included in the default schema -- only standard Jira fields are synced
• Sprints are fetched per board; ensure boards are configured in your Jira projects
• Worklogs and comments reference issues via issue_id and issue_key

Static IPs for Allowlisting

If your Jira/Atlassian configuration requires IP allowlisting:

• Production: 34.170.185.84, 35.192.90.94
• Staging: 34.171.93.34