> 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/adding-jira-stories-to-a-branch.md).
# Adding Jira Stories to a Branch
{% 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 explains how to add Jira stories to a DevOps branch. Once added, the Jira story's status will automatically update to the mapped status whenever the branch is deployed to an organization configured in the Jira integration with Status Mapping. For more details on how status mapping works, see the following article.
* [Overview of Jira Integration](/devops/settings/jira-integration/overview-of-jira-integration.md)
## Adding Jira Stories
{% stepper %}
{% step %}
### Select a Branch
1. Click **Code** from the left sidebar menu.
2. Click the branch to add a Jira story to.
{% endstep %}
{% step %}
### Add Stories
1. Click the **Related stories** tab.
2. Click **Add stories**.
3. Click the **Integration** dropdown menu.
4. Select the Jira integration to add stories from.
5. Click the **Project** dropdown menu.
6. Select the Jira project to add stories from.
{% hint style="info" %}
To add stories from different Jira projects, add the stories from each project separately by following the instructions in this section.
{% endhint %}
7. Click the **Stories** dropdown menu.
8. Select each of the stories to add to this branch.
{% hint style="info" %}
#### Selecting Stories
Only the Story Key is displayed for each story in the list. If you need to identify which Story Keys correspond to the stories you're looking for, you'll need to reference your Jira project directly.
Click a Jira story in the dropdown menu to select it, and a check mark will appear to the right. You can select multiple stories at once. To unselect a story, click it again to remove the check mark. If you have many stories, use the search bar to find them quickly.
{% endhint %}
9. Once you have selected the stories, click outside of the menu to close it.
10. Click **Add** to add the selected stories.
{% endstep %}
{% step %}
### Confirm Added Stories
1. Once the stories are added, they are listed in the **Related Stores > Jira** table along with details about each story.
2. Confirm that the stories you added are correct.
3. The status of these stories will be updated whenever this branch is deployed to an organization that has a mapped status update.
{% 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/adding-jira-stories-to-a-branch.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.
