Docs / Connecting Jira

Connecting Jira

API token auth, the current search endpoint, and how status changes work without a plain status field.

Set up

  1. In Jira: id.atlassian.com → Security → API tokens → Create and manage API tokens.
  2. In Z3NTRA: Systems → Connect a system → Jira.
    • Site — your yourcompany.atlassian.net subdomain, or a full site URL.
    • Email — the account the token belongs to.
    • API token — from step 1.
  3. Test connection, then Add system.

What gets pulled in

By default: issues assigned to you that aren't in a "Done" status category, most-recently-updated first. Override the underlying JQL under Advanced if you want a different scope.

What write-back changes

Title, description, deadline, and priority write directly. Description is round-tripped through Atlassian's document format — plain text in, simple paragraphs out.

Status is differentJira has no plain status field to set — a status change goes through the separate transitions API instead (Z3NTRA looks up the available transitions on that issue and fires the one that lands on the target status category). If nothing matches, you'll see a warning asking you to name a transition explicitly under Advanced.

Jira's five-level priority scale (Highest…Lowest) maps onto 1–5, the same "lower number, higher importance" convention Azure DevOps uses.

← Connecting Monday.com Connecting Zendesk →