> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/integrations/project-management/jira.md).

# Jira

<div align="left"><img src="/files/d1BurkJmLf0GdcSZPUoE" alt=""></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect Jira**

* Find the **Jira** integration module under the **Project management** section
* Click the **Connect** button
* You’ll be taken through a standard Jira app OAuth flow
  * Select a specific Jira org if you’re a member of multiple (otherwise will be pre-selected)

{% hint style="warning" %}
You must be logged in as a Jira user with read/write permissions in the selected Jira org.&#x20;

The Jira user that performs the OAuth needs to be granted the  `ADMINISTER_PROJECTS` permission in each project from which you want to pull tickets. Make sure that this permission is assigned directly within Jira for all relevant projects.
{% endhint %}

{% hint style="info" %}
Jira OAuth is "user bound", meaning all actions taken via the integration are associated to the Jira user that was used during the installation flow. Teams typically create a dedicated service account user for this purpose.
{% endhint %}

* Jira redirects you back to Runway, Runway presents a dialog:
  1. Select all the Jira projects you want to pull tickets from
  2. Select any additional columns that signify a “done” state for your tickets (Runway pre-selects any columns marked in Jira as “done” states)
  3. Select any additional fields that you want to make available for filtering and visible in ticket details&#x20;

{% hint style="info" %}
Runway also supports Jira Personal Access Token (PAT) authentication. If you would prefer to leverage this option, please [get in touch](mailto:hello@runway.team).
{% endhint %}

### Add feature affiliations

* Specify the labels and/or fix versions that Runway should use to associate tickets with specific releases
* Pattern is tokenized with the release version, *e.g.* `ios-{version}`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.runway.team/integrations/project-management/jira.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.