feat(skills): add JIRA issue creation skill with relocation notice

[Anthony Vollmer (avollmer-redhat)]

Summary

Adds the create-jira-issue skill aligned with the ARO HCP JIRA governance policy. This is a temporary copy -- the canonical home for all JIRA governance skills is being established in aro-ai-tools, and this skill will be relocated there.

What's included

• Oncall investigation sub-task structure (Investigation, Mitigation, Follow-up) so each contributing engineer gets credit
• Activity Type taxonomy labels for reporting (s360sreoperability, engineeringoperability, customerexperience, customerfeature)
• Release Pending and Blocked status in workflows
• 90-day policy staleness self-check against the governance Google Doc
• Relocation notice pointing to aro-ai-tools for the companion jira-workflow and groom-jira skills

What's NOT included (lives in aro-ai-tools)

• jira-workflow skill (status lifecycle, Feature/Initiative management)
• groom-jira skill (stale ticket detection, close policy, weekly status prep)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: avollmer-redhat
Once this PR has been reviewed and has the lgtm label, please assign geoberle for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• tooling/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Copilot]

Pull request overview

Adds a new triage skill (create-jira-issue) intended to standardize creation of AROSLSRE JIRA issues (including oncall investigation structure) and to note planned relocation of the canonical governance skills to aro-ai-tools.

Changes:

• Introduces create-jira-issue skill documentation covering required fields, labels, components, sprint lookup, and workflows.
• Adds a relocation notice pointing to aro-ai-tools for related JIRA governance skills.

Suppressed comments (2)

tooling/triage/skills/create-jira-issue/SKILL.md:113

• The issue-type table lists Spike as if it were its own JIRA issue type, but later notes say spikes must be created as Story with a spike label. This is easy to misread and could lead to creating the wrong issue type.

| **Spike** | Time-boxed research to help the team make better decisions. Use for investigatory work with unclear scope. | 10009 |

tooling/triage/skills/create-jira-issue/SKILL.md:303

• Inside the description template code fence, the example entry uses backslash-escaped backticks (e.g. \``). If someone copies the template into a JIRA description, those backslashes will remain and the example won’t render as code fences. Using ~~~` fences inside the template avoids the need for escaping and stays copy/paste-friendly.

\`\`\`
### Q1: KMS container events in CI namespaces

**Command**:
\`\`\`kql

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (4)

tooling/triage/skills/create-jira-issue/SKILL.md:105

• The issue-type table lists "Spike" as if it were a distinct issue type while also reusing the Story ID. Since the guidance is to create Spikes as Story + spike label, make that explicit in the table row to prevent confusion.

| **Spike** | Time-boxed research to help the team make better decisions. Use for investigatory work with unclear scope. | 10009 |

tooling/triage/skills/create-jira-issue/SKILL.md:698

• Markdown guidance is incorrect: in Markdown, single asterisks render italics, not bold. This line should describe bold as using double asterisks.

   - Bold: use single asterisks `*bold*`

tooling/triage/skills/create-jira-issue/SKILL.md:530

• This example uses a bare URL, but the skill’s Markdown guidance says to avoid pasting bare full URLs and use [text](url) instead. Update the example (or relax the rule) so the guidance is internally consistent.

- *JIT Request URL*: https://jitaccess.security.core.windows.net/...

tooling/triage/skills/create-jira-issue/SKILL.md:87

• issue_type lists "Spike" as an option, but later steps specify Spikes should be created as a Story with a spike label (i.e., there is no distinct Spike issue type to pass to the create-issue call). Clarify this in the parameter description to avoid an agent attempting issueTypeName: Spike.

This issue also appears on line 105 of the same file.

| `issue_type` | no | Story (default for most work), Task (small self-contained), Bug (confirmed defects), Spike (time-boxed research) |