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
Enable Jira Integration in project settings
Install Currents for Jira from Atlassian Marketplace
Link the accounts with installation token
See the Setup Guide for complete instructions.
Usage
Create Issues from test failures with full failure details
Link test failures to existing issues
See the Usage Guide for details.
Limitations
See Usage
Security & API Access
The Jira integration is designed so that programmatic access - including through the REST API and the MCP Server - 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. 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 application requests the following Atlassian scopes, which apply to the organization integration as a whole (dashboard, REST API, and MCP alike):
read:jira-workread:jira-userwrite:jira-workmanage:jira-projectread: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.
Last updated
Was this helpful?
