> 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-a-jira-integration.md).
# Adding a Jira Integration
{% 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 connect your Jira account to DevOps so that issue statuses update automatically. This keeps your Jira workflow aligned with actual delivery progress in DevOps.
After adding a Jira connection, configure it by following the instructions in the articles below.
* [Adding Projects to a Jira Integration](/devops/settings/jira-integration/adding-projects-to-a-jira-integration.md)
* [Configuring a Jira Project](/devops/settings/jira-integration/configuring-a-jira-project.md)
## Creating an Atlassian/Jira API Token
{% stepper %}
{% step %}
### Access API Tokens Page
1. Log in to your Jira account.
2. Access your Atlassian **Account settings**.
3. Click the **Security** tab.
4. Click the **Create and manage API tokens** link in the **API tokens** section.
{% endstep %}
{% step %}
### Create API Token
1. Click **Create API token**.
2. Enter a **Name** for the API token.
3. Select the **Expires on** date for the token.
4. Click **Create**.
5. Click **Copy** to copy the **API token**, then save it in a safe place. This token is only displayed once and can't be recovered.
{% hint style="info" %}
The **API token** you created will be used when adding a Jira integration in DevOps.
{% endhint %}
6. Click **Done**.
{% endstep %}
{% endstepper %}
## Adding a Jira Integration
{% stepper %}
{% step %}
### Access Integration Settings
1. Click **Settings** from the left sidebar menu.
2. Click the **Integrations** tab.
3. Click **User stories integrations**.
{% endstep %}
{% step %}
### Add Jira Integration
1. Click **Add Integration**.
2. Enter a descriptive name for the integration in the **Name** textbox.
3. Click the **Service type** dropdown menu.
4. Select **Jira**.
5. Click the **Authorization** dropdown menu.
6. Select **Basic Auth**.
7. In the **Username** textbox, enter the Jira username for the account that created the API token in the section above.
8. In the **Password/Token** textbox, enter the Atlassian API token you created in the section above.
9. In the **Instance URL** textbox, enter the URL for your Atlassian/Jira instance.
{% hint style="info" %}
#### Instance URL
Your Jira instance URL follows the format `https://[company-domain].atlassian.net`. To find it, check your browser's address bar when logged in to Jira.
{% endhint %}
10. Click **Add integration**.
11. Once added, the Jira integration will be listed on the Integrations page.
{% 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-a-jira-integration.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.
