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

# Usage

Learn how to use Currents Jira Integration

Once enabled, you can create new or link an existing Jira issue directly from test execution details in Currents. You can also explore previously created or linked issues that are linked to the current test.

## Browse Linked Jira Issues

1. Open any test execution details in Currents
2. Look for the **Jira** icon (only visible when integration is enabled). If there existing (previously linked) Jira Issues related to the test, you will see a counter next to Jira icon.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FZoPFEhk3VuB4uX5sik5O%2Fcurrents-2025-10-13-21.59.36%402x.png?alt=media&amp;token=74fd77aa-f07c-414f-b344-4a38b54330ac" alt=""><figcaption><p>A test has 2 linked Jira Issues</p></figcaption></figure>

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FsxYzTqGQeZ1y3LXRvhoP%2Fcurrents-2025-10-13-21.56.30%402x.png?alt=media&amp;token=cc9d718d-368a-4bfc-9a13-035ba06ce10e" alt=""><figcaption><p>A test has no existing Jira Issues</p></figcaption></figure>

By clicking on the icon you can:

* Explore linked Jira Issues
* Create a new Jira Issue
* Link an additional existing Issue

## Create a New Jira Issue

To create a new issue:

1. Select the **Jira Project** and **Issue Type**
2. Enter **Issue Title** and **Description** (optional)
3. Toggle **Include Details** to automatically add test context (error messages, stack traces, etc.)
4. Click **Create Issue**

Example of a newly created issue:

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FxoH7uLph7L3yRnCAt7Wd%2Fcurrents-2025-07-11-15.41.48%402x.png?alt=media&amp;token=c3b016d5-bb97-4ca3-8ace-ef597c78d297" alt="Example of New Jira Issue creation form"><figcaption><p>Example of New Jira Issue creation form</p></figcaption></figure>

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FFhh4n6L29JOLiCG3re9J%2Fcurrents-2025-07-11-15.42.28%402x.png?alt=media&amp;token=f79488aa-c175-405d-bde9-dcc3ce70e1fd" alt="Example of an new Jira issue created from Currents"><figcaption><p>Example of an new Jira issue created from Currents</p></figcaption></figure>

## Link an Existing Jira Issue

To link and comment on an existing issue:

1. Select a **Jira Project**
2. Search for the issue by typing its title (results limited to 50 items)

   *Note: For more specific results, use more detailed search terms.*
3. Enter your comment text
4. Toggle **Include Details** to add test context
5. Click **Add Comment**

Example of commenting on an existing issue:

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FHKTkw2f1rpQlLZpQ1cxh%2Fcurrents-2025-07-11-15.45.42%402x.png?alt=media&amp;token=348a14a2-867c-49c2-9c84-a40d4ae12570" alt="Example of linking test failure to an existing Jira issue"><figcaption><p>Example of linking test failure to an existing Jira issue</p></figcaption></figure>

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FwRTsf2k1wDlHpwJCkfC0%2Fcurrents-2025-07-11-15.47.01%402x.png?alt=media&amp;token=c8bf071a-c131-44b3-9ba6-0e003bc69736" alt="Example of a Jira issue comment originating from Currents"><figcaption><p>Example of a Jira issue comment originating from Currents</p></figcaption></figure>

### Browsing Linked Jira Issues

Open Jira dialog to list existing Jira Issues linked to the current test.

* Click on the Jira Issue ID to explore its details (opens a new tab)
* Click 💬 to add a new comment to an existing issue
* Click ⛓️‍💥 to unlink Jira Issue from the test
* Click **Add Jira Issue** to create new or link an additional Jira Issue

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fi3BGJvEwlWwOTpEGLJJQ%2Fcurrents-2025-10-13-22.11.37%402x.png?alt=media&amp;token=2cb4e9c3-810e-49ff-b3ef-015f3548efe8" alt=""><figcaption><p>Listing Jira Issues related to the test</p></figcaption></figure>

### Notes

* The integration creates one-way links from Currents to Jira
* Deleting or closing Jira Issue do not remove those issues in Currents - you will need to do that manually
* Comments include a link back to the relevant test in Currents


---

# 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.currents.dev/resources/integrations/jira/usage.md?ask=<question>&goal=<user_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.
