What is create-jira-items?

Rules for creating Jira features, epics, stories, tasks, and bug tickets, including project, component, label, security, and formatting requirements.

Use them when creating or drafting Jira work items, especially HyperShift and OpenShift bug reports.

They reduce setup mistakes and help keep tickets consistent with the correct Red Hat OpenShift project and security rules.

create-jira-items — Cursor rule for Cursor by openshift/hypershift

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.

Clone the repo

git clone --depth 1 https://github.com/openshift/hypershift

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/openshift/hypershift/create-jira-items/github.svg)](https://agentmods.dev/rules/openshift/hypershift/create-jira-items)

Your own site

<a href="https://agentmods.dev/rules/openshift/hypershift/create-jira-items"><img src="https://agentmods.dev/badge/rules/openshift/hypershift/create-jira-items/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/rules/openshift/hypershift/create-jira-items"><img src="https://agentmods.dev/badge/rules/openshift/hypershift/create-jira-items.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 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,266 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.00051	$0.01266
Opus 5.5	$0.00020	$0.00506
Sonnet 5.5	$0.00010	$0.00253
Haiku 4.5	$0.00005	$0.00127

Measured 1mo ago against content hash 916c6641bf4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-jira-items 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 1mo 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/create-jira-items.mdc · 122 lines

How it starts

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

General

You should try to use a Jira MCP server to create any Jira items or issues.

Any HyperShift feature, epic, story, or task should be created in the Jira project known as Red Hat OpenShift Control Planes also known as CNTRLPLANE.

Any request to make a bug ticket or make the content for a bug ticket should go under the Jira project known as OpenShift Bugs, also known as OCPBUGS.

Set the Jira component to:

HyperShift / ARO - when the issue is about ARO HCP
HyperShift / ROSA - when the issue is about ROSA HCP
HyperShift - when it is not clear if the issue is about a particular HyperShift platform

When you create a Jira issue, add this label: ai-generated-jira.

By default, set the Security Level to the following: Red Hat Employee.

Never include credentials or secrets in any Jira issue (e.g., usernames/passwords, cloud keys, API tokens, kubeconfigs, SSH keys, certificates). This applies to descriptions, comments, attachments, screenshots, logs, and URLs. Redact before sharing.

Use Jira’s native description formatting (Wiki/ADF): headings, bullet lists, code blocks, and tables.

Standard Parts of a Jira Issue

Summary

A summary is a brief text synopsis of the issue.

It answers the questions - How do we typically refer to this issue?

A summary is needed for the following Jira issue types: Outcomes, Features, Initiatives, Epics, Stories, Spikes, Tasks, Bugs, Tickets, Risks, Sub-Tasks.

Setting Versions

For any Jira story or task, unless specified differently from the user, the target version (also known as customfield_12319940) should always be openshift-4.21.

For any OCPBUGS Jira issue, the affected version/s and target version (also known as customfield_12319940) fields should default to 4.21.

Never set the Fix Version/s or fixVersions fields.

Instructions on specific Jira Issue components

Creating a feature

TBD

Creating an epic

Summary: An agile epic is a body of work that can be broken down into specific items (called user stories) based on the needs/requests of customers or end-users. Epics are an important practice for agile and DevOps teams. When adopting agile and DevOps, an epic serves to manage work.

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

1mo ago First seen · 122 lines · 51 tokens per session scan A 916c6641bf4f

Subscribe to this mod's changes

create-jira-items is a cursor rule published in the GitHub repository openshift/hypershift (547 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 1,266 once invoked, about $0.0002 per session on Opus 5.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

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

create-jira-items