Integrate Jira with Astra

Last updated: October 30, 2026

Connecting Jira turns the vulnerabilities Astra finds into Jira issues and keeps both sides in sync. Each Astra target sends its findings to one Jira project. Astra creates the issues, updates their status and priority, and copies comments. With the Jira webhook also set up, status changes and comments made in Jira come back into Astra. This article covers connecting Jira, the Jira card and linking targets to Jira projects. Each of the other tasks has its own article, listed under What to do next.

Availability: Jira needs an active plan with at least one active target. If your plan doesn't cover it, the Integrations page shows Integrations aren't on your plan. with a View plans link to upgrade.

Before you start

  • A Jira account and API token. Astra signs in to Jira with a user email and an API token, not a password. The Jira user needs access to every Jira project that targets will send findings to.

  • Jira admin rights for two-way sync. Creating the webhook in Jira needs the Administer Jira global permission. One-way sync from Astra to Jira works without it.

  • Room on the plan. Each workspace can connect a set number of tools. When that number is used up, connecting shows Integration limit reached. Remove a connection the workspace no longer uses, or upgrade the plan from View plans.

Connect Jira

  1. Go to Integrations. Jira is listed under Project Management Tools and on the All Integrations tab. Click Connect on the Jira card.

The Integrations page on the Project Management Tools tab, with the Jira card and its Connect button.

  1. A panel opens with an overview of what Jira does in Astra. Click Connect at the bottom.

The Jira overview panel with its feature images, developer details and the Connect button.

  1. The Connect Jira form opens. Fill in:

    • Jira instance: Cloud for Jira sites on atlassian.net (the default), or Server for a self-hosted Jira.

    • Jira URL: the address of the Jira site, for example https://your-domain.atlassian.net.

    • User email: the email of the Jira user Astra signs in as.

    • API token: an API token for that user. See Get a Jira API token.

The Connect Jira form with the Jira instance, Jira URL, User email and API token fields.

The Jira instance list, with Cloud and Server.

The Connect Jira form filled in, ready for Connect and pull projects.

  1. Click Connect and pull projects. Astra checks the details with Jira and reads the list of Jira projects. When it works, Astra shows Jira Integration has been created and opens Astra Targets and Jira, where targets are linked to Jira projects.

If Jira rejects the details, Astra removes the half-created connection and shows Integration removed because activation failed. For the common causes, see Fix a Jira connection error or replace the API token.

Get a Jira API token

Hover How do I get this? next to API token for the steps, or click Get API Token in that panel to open the Atlassian token page.

  1. Open the Atlassian account settings and go to Security.

  2. Select Create and manage API tokens, then Create API token.

  3. Give the token a label that's easy to recognise, then copy it and paste it into API token.

The How to get an API token panel, with three steps and the Get API Token button.

Note: Atlassian API tokens can expire. When a token expires, sync stops until a new token is saved from View connection (see Fix a Jira connection error or replace the API token).

The Jira card

Once connected, Jira moves to Active Integrations. The card shows the Jira site address and a status badge:

  • Connected: Astra can reach Jira.

  • Connection Error: Astra couldn't reach Jira just now, for example because the API token expired or the site is down (see Fix a Jira connection error or replace the API token).

  • Paused: someone paused the connection.

  • Failed: the connection stopped working and needs attention.

The card also shows Jira projects in use, Astra Targets linked and Last sync (the date Astra last synced with Jira, or Never). View connection opens the connection details, and Configure sync opens Astra Targets and Jira. The ⋮ menu has Pause integration (or Unpause integration) and Delete integration (see Pause, remove a target's link, or delete the Jira connection).

The Jira card with the Connected badge, the Jira site address, 1 of 1 Jira projects in use, 1 of 5 Astra Targets linked and Last sync Never.

The Jira card after a sync, with Last sync showing 28 Oct, 2026.

Astra Targets and Jira lists the workspace's active targets, one row each. "Every Astra Target sends its findings to one Jira project." Several targets can send their findings to the same Jira project.

  • Astra Target: the target's name.

  • Jira project: the linked Jira project's key and name with a Change link, or Not linked to a Jira project.

  • The search box (Search Astra Targets), the Target type filter and the Jira: All / Jira: Linked / Jira: Not linked filter narrow the list.

Astra Targets and Jira filtered to Jira: Linked, with two targets linked to the KAN project.

The Jira filter open, with Jira: All, Jira: Linked and Jira: Not linked.

For a target that isn't set up yet, click Configure. The arrow next to it offers Configure from scratch or Copy from a target already set up (once at least one other target is configured). The six setup steps that follow are covered in Configure Jira sync for a target.

The arrow next to Configure, with Configure from scratch and Copy from a target already set up.

For a target that's already set up, click Edit config to change it, or use ⋮ > Remove link to unlink it (see Pause, remove a target's link, or delete the Jira connection).

Astra Targets and Jira after saving a setup, with one target linked to SCRUM (Astra Docs Test), its Change link and Edit config button, and the Jira project config updated successfully message.

Edit config opens the same six steps with the saved choices filled in, starting at Jira project with the linked project already picked.

Set up Jira sync opened from Edit config, with the SCRUM project already selected.

What to do next

FAQ

Can Astra see every project in the Jira site?

Astra uses the Jira user's access to list projects, but it only creates and updates issues in the projects linked to targets. The webhook's JQL limits what Jira sends back to the linked projects.

If a Jira issue is moved to Done or Closed, does the Astra vulnerability close too?

Not straight away. A vulnerability is marked Solved only after a rescan confirms the fix, so Solved can't be picked on the Jira to Astra side. Map Done (or Closed) to Under Review instead. With two-way sync on, closing the issue moves the vulnerability to Under Review, and on plans with automatic rescans Astra rescans it. Without the webhook, or without that mapping, the vulnerability stays as it is in Astra (see Turn on two-way sync with the Jira webhook).

Does changing the assignee or priority in Jira update Astra?

No. Only status changes and comments come back from Jira. Priority travels one way, from Astra severity to Jira priority.