Jira support

Last updated date:

Connect, reconnect, and troubleshoot Jira without sharing credentials or customer content through support channels.

1. Before you start

  • Create a Jira Cloud OAuth 2.0 (3LO) app with the exact callback URL used by your Seedling environment.
  • Request read:jira-work, read:jira-user, and offline_access.
  • Authorize with a Jira user who can read every intended project and issue.
  • Do not send Jira credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Jira OAuth 2.0Atlassian's official Jira Cloud OAuth 2.0 (3LO) guide.

2. Connect Jira

  1. Complete the Atlassian authorization-code flow and exchange the code for access and refresh tokens.
  2. In Seedling, open Connections, select Jira, and choose personal or workspace scope.
  3. Paste both tokens and provide the cloud ID only when the grant can access multiple Jira sites.
  4. Connect, confirm the resolved site, and allow project and issue synchronization to complete.

3. Authorization and connection problems

Multiple accessible sites
Provide the exact Jira cloud ID so Seedling does not guess which site the connection should own.
Refresh rejected
Repeat the authorization flow with offline_access and replace both access and refresh tokens.
Project or issue forbidden
Confirm the authorizing Jira user retains native access and that issue security or project permissions allow the read.

4. Missing or delayed data

  1. Confirm the affected project belongs to the verified cloud ID.
  2. Confirm the authorizing Atlassian user can open the issue, comment, or attachment in Jira.
  3. Check project permissions, issue-security levels, archived projects, and removed users before treating the record as missing.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Repeat the Atlassian authorization-code flow for the same app, scopes, user, and cloud site.
  2. Replace the access and refresh tokens on the exact Seedling connection.
  3. Confirm Seedling resolves the same cloud ID before retiring the old authorization.