> ## Documentation Index
> Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> Push Plans from Lane into Jira as issues, so what you've decided to build lands in your engineering backlog.

<Frame>
  <img src="https://mintcdn.com/lane/-ScU87ndAo9rXf8V/images/lanexjira.jpg?fit=max&auto=format&n=-ScU87ndAo9rXf8V&q=85&s=5a8f1c8676dc2742ead2665af9df3d0f" alt="Integrating Jira with Lane for managing product delivery" width="2980" height="1702" data-path="images/lanexjira.jpg" />
</Frame>

Lane's Jira integration connects product planning to engineering delivery: push a [Plan](/docs) from Lane into Jira as an issue, so the work you've decided on lands in your team's backlog with its context intact.

Available on **Pro and Business**.

## Connect

Go to **Settings → Integrations → Jira** and connect via OAuth.

## Push a Plan to Jira

From a Plan, use **Send to → Jira**. Lane creates a Jira issue from the Plan and links the two. The linked issue — and its current Jira status — show in the Plan's delivery drawer, so you can see where the work sits from inside Lane.

## Push-only

Unlike [Linear](/linear), [Asana](/asana), and [Notion](/notion), the Jira integration is **push-only** today: a Plan's status isn't updated from Jira, so Jira doesn't drive [closing the loop](/close-the-feedback-loop). Use it to get work into Jira; track delivery status in Jira itself.

## FAQs

**Q: What gets created in Jira when I push a Plan?**\
A: A Jira issue, linked back to the Plan.

**Q: Does the Plan's status update from Jira?**\
A: No — Jira is push-only. The Plan shows the linked issue's status for reference, but Jira doesn't sync status onto the Plan or trigger close the loop.

**Q: Which plans include Jira?**\
A: Pro and Business.
