What is jira-workflow?

A set of instructions for handling Jira, a tool for tracking software work, through connected tools. It covers finding, viewing, searching, updating, and creating tickets.

Use it to view assigned or sprint tickets, search issues, read ticket details and comments, update tickets, create tickets, and report bugs.

It gives common Jira tasks a defined process and requires Jira credentials to work.

jira-workflow — Cursor rule for Cursor by kubev2v: A set of instructions for handling Jira, a tool…

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.

agentmods

npx agentmods add rules/kubev2v/forklift-console-plugin/jira-workflow

Clone the repo

git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

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/rules/kubev2v/forklift-console-plugin/jira-workflow.svg)](https://agentmods.dev/rules/kubev2v/forklift-console-plugin/jira-workflow)

Your own site

<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/jira-workflow"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/jira-workflow.svg" alt="Measured on agentmods" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. Scan, not verified.

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	$0.00008	$0.01131
Opus 5	$0.00004	$0.00566
Sonnet 5	$0.00002	$0.00226
Haiku 4.5	$0.00001	$0.00113

Measured 3d ago against content hash c8e6d82eb6b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

jira-workflow 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 3d 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.

.cursor/rules/workflows/jira-workflow.mdc · 186 lines

How it starts

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

Jira Workflow

Invoke with: "get my tickets", "show sprint issues", "update ticket", "search jira", "create a ticket", "report a bug"

This workflow covers Jira MCP operations. For the full development workflow (ticket to PR), see feature-development.mdc.

Prerequisites

Jira MCP tools require .cursor/mcp.json (gitignored). Configure it with your Jira credentials before using Jira commands. Without it, Jira-related invocations will not work.

1. Finding Tickets

Get My Assigned Tickets

"Show my assigned tickets"

Uses jira_search with JQL: assignee = currentUser() AND status != Done AND project = MTV

Get Current Sprint Tickets

"Show current sprint tickets"

Uses jira_get_sprint_issues

Search for Specific Tickets

"Find open bugs in MTV project"

Uses jira_search with appropriate JQL

Get Ticket Details

"Get details for MTV-1885"

Uses jira_get_issue + jira_get_issue_comments

2. Common JQL Queries

By Status

assignee = currentUser() AND status = "In Progress" AND project = MTV
status = "Ready for Dev" AND project = MTV
status = "Code Review" AND assignee = currentUser() AND project = MTV

By Type

issuetype = Bug AND project = MTV AND status != Done
issuetype = Story AND assignee = currentUser() AND project = MTV

By Time

updated >= -7d AND assignee = currentUser() AND project = MTV
created >= startOfWeek() AND project = MTV

By Component

component = "User Interface" AND project = MTV AND status != Done

3. Updating Tickets

Add a Comment

"Add comment to MTV-1885: Started investigating the issue"

Uses jira_add_comment

Update Status

"Move MTV-1885 to Code Review"

Uses jira_transition_issue

4. Creating Tickets

Bug Ticket Flow

When reporting a bug, gather:

Summary: One-line description (e.g., "Provider list doesn't load after page refresh")
Affected Version: Which version (e.g., "2.7.0")
Steps to Reproduce: Numbered list
Expected vs Actual Behavior
Priority: Blocker/Critical/Major/Minor/Trivial

Read the full file on GitHub · 186 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.

3d ago First seen · 186 lines · 8 tokens per session scan A c8e6d82eb6b7

Subscribe to this mod's changes

jira-workflow is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,131 once invoked, about $0.0000 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-08-30.

Project management

jira-workflow