What is jira-to-testrail?

A workflow for turning Jira tickets into TestRail test cases. Jira is a tool for tracking work, while TestRail is a tool for organising software tests.

Use it when you need to create TestRail cases from one or more Jira tickets, provided the required connections and destination are available.

It helps QA teams convert a ticket's acceptance criteria into recorded test cases without copying the details by hand. It requires connected Jira and TestRail tools and a destination section.

jira-to-testrail — Skill for Claude Code and Codex by adakh3

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add adakh3/testrails-mcp --skill jira-to-testrail

Clone the repo

git clone --depth 1 https://github.com/adakh3/testrails-mcp

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/adakh3/testrails-mcp/jira-to-testrail/github.svg)](https://agentmods.dev/skills/adakh3/testrails-mcp/jira-to-testrail)

Your own site

<a href="https://agentmods.dev/skills/adakh3/testrails-mcp/jira-to-testrail"><img src="https://agentmods.dev/badge/skills/adakh3/testrails-mcp/jira-to-testrail/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/adakh3/testrails-mcp/jira-to-testrail"><img src="https://agentmods.dev/badge/skills/adakh3/testrails-mcp/jira-to-testrail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,464 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00096	$0.01464
Opus 5	$0.00048	$0.00732
Sonnet 5	$0.00019	$0.00293
Haiku 4.5	$0.00010	$0.00146

Measured 11d ago against content hash 326a9ccd20fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

jira-to-testrail scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/jira-to-testrail/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Jira → TestRail case generator

Convert acceptance criteria from a Jira ticket into TestRail test cases under a chosen section.

Preconditions — check before doing anything else

A Jira tool must be available in this session. Look for any tool exposing Jira issue reads (e.g. mcp__atlassian__getJiraIssue, mcp__jira__get_issue, etc.). If none exists, stop and tell the user: "I need a Jira MCP connected to read the ticket. Please install one (e.g. Atlassian's official MCP) and re-run."
The TestRail MCP must be available (tools prefixed with mcp__testrails__ such as list_projects, add_case). If not, stop and tell the user to install/register testrails-mcp.
The user must have provided a destination. See Step 0 below — do not skip it.

Inputs to gather

jira_key — e.g. PROJ-1234. Accept a full URL too and parse the key out.
section_id — TestRail section the cases will be created under. Required.
suite_id (optional) — only relevant for multi-suite projects. If unsure, infer from the section.

Step 0 — Establish the destination (do this first, always)

Before reading the Jira ticket, before doing anything else, confirm you have a section_id.

If the user provided a numeric section_id (e.g. "section 47", "under section_id 47"): use it. Skip to Step 1.

If the user provided names instead of an ID (e.g. "the Authentication section in the Login suite of the Mobile App project"): resolve them via list_projects → list_suites → list_sections. Once you have the section_id, confirm the resolved path back to the user in one line ("Found: Mobile App › Login › Authentication (section 47). Proceed?") and wait for yes before continuing.

If the user provided no destination at all: do NOT guess, do NOT pick a default, do NOT proceed to read the ticket. Ask. Walk them through it interactively:

Call list_projects and present the list as a numbered menu. Ask which project.
After they pick, call list_suites(project_id). If exactly one suite exists, use it silently. If more than one, present as a numbered menu and ask.
Call list_sections(project_id, suite_id). Present as a numbered menu (indent nested sections to show hierarchy). Ask which section.
Confirm the full path back to them and wait for explicit "yes" before moving on.

Read the full file on GitHub · 98 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 98 lines · 96 tokens per session scan A 326a9ccd20fa

Subscribe to this mod's changes

jira-to-testrail is a skill published in the GitHub repository adakh3/testrails-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 1,464 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jira-to-testrail