jira-aipcc-create

Files (1)

• SKILL.md

SKILL.md (first lines)

# Create AIPCC Jira Issue

Create Jira issues in the AIPCC project using the `acli` CLI.

## Prerequisites

- `acli` must be installed and authenticated (`acli jira auth`)

## Implementation

### Step 1: Infer Issue Details from Context

Analyze the conversation to determine:

1. **Summary**: A concise title (under 100 characters) describing the issue
2. **Description**: A Markdown description with relevant context, root cause, fix details, or requirements (use Markdown)
3. **Type**: One of the following based on the nature of work
   - `Bug`: problem that impairs or prevents product functions; tracks escaped defects
   - `Story`: action-oriented, smallest unit of work that can be completed within one sprint
   - `Epic`: large user story that needs to be broken down; groups bugs, stories, and tasks to show progress of a larger effort; represents significant deliverable; does not span teams
   - `Feature`: use when tracking capability or well-defined set of functionality delivering business value; can include additions/changes to existing functionality
   - `Spike`: time-bound unit of work representing research-related task; not easy to size
   - `Initiative`: use when capturing internal improvements
   - `Task`: unit of work to be accomplished, not end-user facing
4. **Component**: One of the valid AIPCC components:
   - `PyTorch`
   - `AIPCC Productization`
   - `Accelerator Enablement`
   - `Wheel Package Index`
   - `AI Testing + Workflow Validation`
   - `Model Validation`
   - `Development Platform`

5. **Parent Epic** (optional): If the user specifies an epic key (e.g. AIPCC-1234), include it as the parent

If any field cannot be confidently inferred, ask the user.

### Step 2: Confirm with the User

Present the proposed issue details to the user in a clear format:

```
I'll create the following AIPCC JIRA issue:

**Type**: Bug
**Component**: Wheel Package Index
**Parent Epic**: AIPCC-1234 (if specified)
**Summary**: Fix duplicate CI pipeline runs
**Description**:
> [description]

Shall I go ahead and create this?
```

Wait for user confirmation before proceeding. If the user requests changes, adjust accordingly.

### Step 3: Create the Issue

Build a JSON file with the following structure.

**Important**: The `description` field MUST be in Atlassian Document Format (ADF), not plain text. `acli` will reject plain text descriptions with an error.

If the user specifies a parent epic, include the `parent` field in `additionalAttributes`. This is the only way to set the epic/parent relationship — `acli jira workitem edit` does not support `additionalAttributes` or custom fields, so the parent must be set at creation time.

```json
{
  "projectKey": "AIPCC",
  "summary": "<summary>",
  "type": "<type>",
  "description": {
    "version": 1,
    "type": "doc",
    "content": [
      {
        "type": "paragraph",
        "content": [
          {
            "type": "text",
            "text": "<description text>"
          }
        ]
      }
    ]
  },
  "additionalAttributes": {
    "components": [{"name": "<component>"}],
    "parent": {"key": "<EPIC-KEY>"}
  }
}
```

Omit the `parent` field from `additionalAttributes` if no epic is specified.

Write it to a temporary file:

```bash
cat > "$(mktemp /tmp/acli-issue-create-XXXX.json)" << 'EOF'
{ ... }
EOF
```

Create the issue using:

```bash
acli jira workitem create --from-json <JSON-FILE>
```

### Step 4: Report Result

On success, `acli` prints the new issue key and URL. Report this to the user:

```
Created AIPCC-12345: https://redhat.atlassian.net/browse/AIPCC-12345
```

Clean up the temporary JSON file after creation.

## Error Handling

From jeremyeder/ai-helpers-plugin, Apache-2.0.

More from jeremyeder/ai-helpers-plugin