jira

Files (1)

• SKILL.md

SKILL.md (first lines)

Jira integration skill for openstack-k8s-operators development workflows.

When invoked directly (`/jira OSPRH-2345`), inspect the ticket and report its type, hierarchy, and linked issues. When used as a reference by other skills, follow the rules below.

## Prerequisites

**Human approval is REQUIRED for all write operations.** Never post comments, create stories, update tickets, or modify any Jira resource without presenting the exact content to the human operator and receiving explicit approval first. Read operations (fetching tickets, inspecting hierarchy) do not require approval.

**ALL Jira comments MUST start with `[AI-GENERATED]` prefix.** This is mandatory and non-negotiable. Never post a comment without this prefix.

## Issue Hierarchy

```
Feature / Initiative
  |
  |  Feature
  |  Initiative
  |
  +-- Epic
  |     |
  |     |  Groups stories/tasks/bugs for a single release
  |     |  Must be scoped to a single release
  |     |
  |     +-- Story / Task
  |     |     Actual engineering work, maps to PR(s)
  |     |     Story and Task are interchangeable
  |     |
  |     +-- Bug
  |           Defect (same level as Story, different workflow)
  |
  +-- Epic
        ...
```

### Key Rules

1. **Sub-tasks are NOT used.** Do not create sub-tasks.

2. **Story and Task are interchangeable.** No semantic difference. Teams may have local conventions, but they are not generalizable.

3. **Outcome comments go on the Story/Task/Bug, never on Epic or Feature.** The Story is where engineering work is tracked. The Epic is a container. The Feature is PM-owned.

4. **If the input ticket is a Feature**, find its child Epics. If there's a relevant Epic, find its Stories. Guide the user down to the right Story to work on.

5. **If the input ticket is an Epic with no child Stories**, check if a Spike exists under the Epic instead. If a Spike is found, warn the user: "This Epic has a Spike (<ticket-id>) but no Story. Spikes are timeboxed research — not implementation work. Do you want to continue planning against the Spike, or create a Story first?" If no Spike and no Story, suggest creating a Story before starting implementation.

6. **Bugs follow their own workflow** (New, Refinement, Planning, Backlog, In Progress, Review, Verified, Closed) but are at the same level as Stories for hierarchy purposes.

7. **Bug-to-Story workflow.** When a Bug has a parent Epic:
   - Check the Epic's children for existing Stories that already cover the fix.
   - If no existing Story covers the fix, suggest creating a Story under the same Epic to track the implementation work. Bugs are typically not added to sprints — Stories are. The Story tracks the engineering work, the Bug tracks the defect.
   - Always ask the user before creating the Story. Present the suggested fields and let them confirm.
   - Once the Story is created and the user confirms, suggest transitioning both the Bug and the new Story to "In Progress" (but only after user approval — never transition tickets without asking).
   - If the Bug has no parent Epic, note this and ask the user whether one should be created or whether to proceed without the Epic hierarchy.

8. **Plan breakdown items become separate Stories under the Epic**, not sub-tasks.

## Ticket Inspection

When given a ticket ID:

1. Fetch the ticket via Atlassian MCP
2. Report: type, summary, status, priority, fixVersion
3. Show hierarchy: parent (Feature/Epic), children (Epics/Stories)
4. Flag hierarchy issues per the rules above

Example output:

```
Ticket: OSPRH-2345
Type: Story
Status: In Progress
Priority: Major
fixVersion: 18.0.1
Summary: Add topology support to GlanceAPI
Parent Epic: OSPRH-1000 (Glance operator enhancements)
Linked Stories: OSPRH-2346, OSPRH-2347

Hierarchy: OK — Story linked to Epic
```

## Operations

### Validate Hierarchy

Before any write operation, that must be approved by the human operator, check the hierarchy:

**Story/Task/Bug — OK to work on:**

```
Hierarchy check for OSPRH-2345:
  Type: Story
  Parent Epic: OSPRH-1000
  Status: OK — proceed with planning/implementation
```

**Bug with parent Epic — suggest Story creation:**

```
Hierarchy check for OSPRH-3456:
  Type: Bug
  Parent Epic: OSPRH-1000 (Glance operator enhancements)
  Sibling Stories: none that cover this fix

  This Bug has a parent Epic but no Story to track the fix.
  Bugs are typically not added to sprints — a Story is needed
  to track the implementation work.

  Suggested Story:
    Project: OSPRH
    Type: Story
    Summary: Fix <bug summary>
    Epic Link: OSPRH-1000
    fixVersion: <from Bug>
    Description: Implementation work for OSPRH-3456

  Create this Story? (y/n)

  After creation, transition both tickets?

From openstack-k8s-operators/devskills, MIT.

More from openstack-k8s-operators/devskills