Currents · Schema
LinkJiraIssueFromRunTestRequest
CompanyTestingPlaywrightTest AutomationCI/CDTest OrchestrationDeveloper ToolsMCP
Properties
| Name | Type | Description |
|---|---|---|
| runId | string | Currents run ID containing the test |
| testId | string | Test ID within the run (client test id) |
| jiraInstallationId | string | Atlassian Jira installation ID for the org integration (same as Installation ID in the dashboard) |
| jiraProjectId | string | Jira project ID for the linked issue |
| jiraIssueType | string | Jira issue type identifier stored on the Currents ticket (same as `jiraIssueType` when creating issues; use issue type discovery when unsure) |
| comment | string | Optional text prepended to the Jira comment and Currents issue description before the automated test context (when `includeContextInComment` is true) |
| includeContextInComment | boolean | When true (default), appends the same automated test context used when creating Jira issues from a run test. When false, `comment` must be non-empty and is used alone for the Jira comment and issue de |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/currents-dev/json-schema/currents-dev-link-jira-issue-from-run-test-request-schema.json",
"title": "LinkJiraIssueFromRunTestRequest",
"x-generated": "2026-11-04",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/currents-dev-openapi.yml#/components/schemas/LinkJiraIssueFromRunTestRequest",
"type": "object",
"required": [
"runId",
"testId",
"jiraInstallationId",
"jiraProjectId",
"jiraIssueType"
],
"properties": {
"runId": {
"type": "string",
"minLength": 1,
"description": "Currents run ID containing the test"
},
"testId": {
"type": "string",
"minLength": 1,
"description": "Test ID within the run (client test id)"
},
"jiraInstallationId": {
"type": "string",
"minLength": 1,
"description": "Atlassian Jira installation ID for the org integration (same as Installation ID in the dashboard)"
},
"jiraProjectId": {
"type": "string",
"minLength": 1,
"description": "Jira project ID for the linked issue"
},
"jiraIssueType": {
"type": "string",
"minLength": 1,
"description": "Jira issue type identifier stored on the Currents ticket (same as `jiraIssueType` when creating issues; use issue type discovery when unsure)"
},
"comment": {
"type": "string",
"description": "Optional text prepended to the Jira comment and Currents issue description before the automated test context (when `includeContextInComment` is true)"
},
"includeContextInComment": {
"type": "boolean",
"default": true,
"description": "When true (default), appends the same automated test context used when creating Jira issues from a run test. When false, `comment` must be non-empty and is used alone for the Jira comment and issue description."
}
},
"allOf": [
{
"if": {
"properties": {
"includeContextInComment": {
"const": false
}
},
"required": [
"includeContextInComment"
]
},
"then": {
"required": [
"comment"
],
"properties": {
"comment": {
"type": "string",
"minLength": 1,
"description": "Required when `includeContextInComment` is false; used alone for the Jira comment and issue description"
}
}
}
}
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/currents-dev-link-jira-issue-from-run-test-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.