> 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.md). # Jira Connect Currents with Jira to create new or link existing issues in Jira without leaving Currents Currents integration with Jira allows teams to create and link test failure details directly from the Currents dashboard. Team members can create new or add comments to existing Jira issues with full context: * error messages, * stack traces, * metadata, * and test history without leaving Currents, eliminating context switching.

The integration is powered by Currents for Jira Application that runs on Jira Cloud.

### Setup 1. Enable Jira Integration in project settings 2. Install Currents for Jira from Atlassian Marketplace 3. Link the accounts with installation token See the [Setup Guide](/resources/integrations/jira/setup.md) for complete instructions. ### Usage * Create Issues from test failures with full failure details * Link test failures to existing issues See the [Usage Guide](/resources/integrations/jira/usage.md) for details. ### Security & API Access The Jira integration is designed so that programmatic access - including through the [REST API](https://docs.currents.dev/api/) and the [MCP Server](/ai/reference/mcp-server.md) - never grants more capability than the dashboard itself: * **Strictly contained to dashboard functionality.** API and MCP access to Jira is limited to the same operations available in the Currents dashboard: listing Jira projects and issue types, and creating or linking issues. There are no additional or privileged Jira operations exposed through the API. * **Jira credentials are never disclosed.** The Jira access tokens used by the integration are stored encrypted and are never exposed through the API, the MCP server, or any response. Requests are proxied through Currents using the organization's configured Jira installation - clients never receive the underlying Jira API keys or tokens. * **Governed by Currents API key permissions.** Jira write operations (creating or linking issues) require a **Read & Write** [Currents API key](/dashboard/administration/api-keys.md). A **Read Only** key can list Jira projects and issue types but cannot create or link issues (requests return HTTP 403). #### Requested Jira scopes The [Currents for Jira](https://marketplace.atlassian.com/apps/1238333) application requests the following Atlassian scopes, which apply to the organization integration as a whole (dashboard, REST API, and MCP alike): * `read:jira-work` * `read:jira-user` * `write:jira-work` * `manage:jira-project` * `read:app-system-token` The integration does not grant any Jira permissions beyond these, and the API cannot expand its own access beyond what the installed Jira app already permits. --- # 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.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.