> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/settings/jira-integration/configuring-a-jira-project.md).
# Configuring a Jira Project
{% hint style="warning" %}
#### Written for the Old UI
This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the [Where Did It Go](/devops/new-ui-ux-transition/where-did-it-go.md) article.
{% endhint %}
##  Overview
This article shows you how to configure a Jira project by mapping organizations to statuses. Status mapping determines which status a Jira story changes to when an organization is deployed. For a more detailed explanation of how status mapping works in the Jira integration, see the following article.
* [Overview of Jira Integration](/devops/settings/jira-integration/overview-of-jira-integration.md)
Once you've configured a Jira project, you must add Jira stories to DevOps branches before DevOps can automatically update story statuses. See the following article for instructions on adding stories to a branch.
* [Adding Jira Stories to a Branch](/devops/settings/jira-integration/adding-jira-stories-to-a-branch.md)
## Configuring a Project
{% stepper %}
{% step %}
### Select Jira Project
1. Click **Settings** from the left sidebar menu.
2. Click the **Integrations** tab.
3. Click **User stories integrations**.
4. Click the Jira integration to configure a project for.
5. Click the Jira Project to configure.
{% endstep %}
{% step %}
### Configure Status Mapping
1. Select an organization from the **Available organizations** list.
2. Click the **Right Arrow** icon to move the selected org to the **Selected organizations** list.
3. Repeat these steps for all organizations that will be mapped to the same status.
4. Click the **Status** dropdown menu.
5. Select the Jira status to map to the organizations you selected.
{% endstep %}
{% step %}
### (Optional) Add Mapping
1. Click **Add mapping**.
2. Select an organization from the **Available organizations** list.
3. Click the **Right Arrow** icon to move the selected org to the **Selected organizations** list.
4. Repeat these steps for all organizations that will be mapped to the same status.
5. Click the **Status** dropdown menu.
6. Select the Jira status to map to the organizations you selected.
{% endstep %}
{% step %}
### Save Configuration
1. Confirm that all of your **Status Mappings** are correct.
2. Click **Save configuration**.
3. To configure other Jira projects, click **Back** to return to the list of Jira projects.
{% endstep %}
{% endstepper %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/devops/settings/jira-integration/configuring-a-jira-project.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
