Jira

Liddr reads issues from the configured project key(s) during ingest, and — for reverse sync — publishes approved requirements back into the project as epics and stories. Both use an Atlassian account email + API token; the token carries that account's Jira permissions.

What Liddr accesses

Direction	Access
Ingest (read into your knowledge graph)	Read-only
Reverse sync (Liddr writing back)	Read & write — only when a Forge action publishes back to this source

Setup

1. In Atlassian: id.atlassian.com → Security → API tokens → Create API token (ideally on a dedicated service account).
2. In Liddr: Settings → Connections → Jira, enter the account email and token and set the Jira base URL (https://<site>.atlassian.net).
3. Set the Project Key(s) in the connector's Advanced settings — comma-separated for multiple projects.
4. Test, then run an Ingest.

Required scopes

Classic API token (recommended)

Ingest — minimum

• No token scopes — access follows the account's Jira permissions
• Account needs: Browse projects on each configured project

Reverse sync — additionally

• Account needs: Create issues in the target project (epics + stories)

TIP

Minimum equals maximum here: restrict the service account to exactly the configured projects via Jira permission schemes — don't use a site-admin account.

API token with scopes

Ingest — minimum

• read:jira-work

Reverse sync — additionally

• write:jira-work

TIP

Choose "API token with scopes" on the same Atlassian page and select Jira. The account's project permissions still apply on top of the scopes.

Reference

• Atlassian docs: manage API tokens