---
title: "Create Jira issue from a run test"
method: POST
path: "/projects/{projectId}/jira/issues"
tags: ["Integrations"]
---

# Create Jira issue from a run test

`POST /projects/{projectId}/jira/issues`

Creates a Jira issue using the organization Jira integration, with title and description built from the specified run and test (same linking behavior as the dashboard). Identifies the Jira site via `jiraInstallationId` (shown in the dashboard as Installation ID). Requires a write-scoped API key. On 404, the `error` field indicates whether the Currents project, Jira installation, run, or test was not found.

## Path parameters

- `projectId` string, required

## Request body

- CreateJiraIssueFromRunTestRequest
  - `runId` string, required — Currents run ID containing the test
  - `testId` string, required — Test ID within the run (client test id)
  - `jiraInstallationId` string, required — Atlassian Jira installation ID for the org integration (same as Installation ID in the dashboard)
  - `jiraProjectId` string, required — Jira project ID in which to create the issue
  - `jiraIssueType` string, required — Jira issue type ID
  - `customFields` object[] — Optional Jira custom fields
    - `fieldId` string, required — Jira field ID (matches `fieldId` from issue type discovery)
    - `value` string, required — String representation for the field value (encoding depends on field type; see Jira custom field docs)

## Response `201`

Jira issue created and linked to the test

- CreateJiraIssueFromRunTestResponse
  - `status` 'OK', required
  - `data` JiraIssueFromRunTestResult, required
    - `jiraIssueKey` string, required — Jira issue key (e.g. PROJ-123)
    - `currentsIssueId` string, required — Currents issue record ID
    - `jiraIssueUrl` string, nullable, required — URL to the Jira issue in the linked Jira instance
    - `currentsIssueUrl` string, required — URL to the Currents dashboard issue modal for the linked test entity

## Other responses

- `400` — Invalid request parameters
- `401` — Authentication failed
- `403` — Insufficient permissions
- `404` — Resource not found
- `409` — Request could not be completed due to a conflict
- `429` — Rate limit exceeded
- `500` — Unexpected server error

---

[API](https://skmtc.dev/currents/apis/currents-rest-api.md) · [All operations](https://skmtc.dev/currents/apis/currents-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/currents/currents-rest-api/revisions/d0e2ed0e7e6a/schema)