Jira Issue Creation

CRITICAL: Scope Limitation

This skill is ONLY for Jira operations. NEVER perform any of the following:

• Code modifications or refactoring
• File creation or editing
• Git operations (branch, commit, etc.)
• Any development work

If the user's request involves both Jira ticket creation AND code work, ONLY create the Jira ticket and report back. Let the parent conversation handle the code work separately.

Pre-Creation Checklist

Before calling createJiraIssue, gather ALL required information:

Cloud ID: 0d334135-ec08-4c00-8411-7a081dce39ca

Issue Type Names (CRITICAL)

Use English names in API calls, not Korean:

Create Issue

Required fields for createJiraIssue:

cloudId: "0d334135-ec08-4c00-8411-7a081dce39ca"
projectKey: "COREPL"
issueTypeName: "<English name>"
summary: "<title>"
description: "<content in Markdown>"
customfield_10468: {"value": "NO"}  # Security & Privacy Review
customfield_10020: <sprint_id>
assignee_account_id: "<accountId>"

For Epics only, add:

• customfield_10011: Epic Name
• labels: Reference similar epics (e.g., ["26H1", "Core", "CorePlatform"])

WARNING: Do NOT include parent field in createJiraIssue - it won't work.

Link to Parent Epic

IMPORTANT: Always display the epic key AND summary (title) so the user can make an informed decision.

Example output before calling editJiraIssue:

상위 Epic 연결: COREPL-YYYY "Epic 제목/이름"

Then use editJiraIssue:

issueIdOrKey: "COREPL-XXXX"
fields: {"parent": {"key": "COREPL-YYYY"}}

Post-Creation

Report with clickable link: [COREPL-XXXX](https://ohouse.atlassian.net/browse/COREPL-XXXX)

Issue Transition

To change issue status:

1. Get transitions: getTransitionsForJiraIssue
2. Call transitionJiraIssue with:
   Copy

   transition: {"id": "<transition_id>"}
   

   • NOT transitionId: "281" (wrong param name)
   • NOT transition: "281" (must be object)

Add Comment

Use addCommentToJiraIssue:

cloudId: "0d334135-ec08-4c00-8411-7a081dce39ca"
issueIdOrKey: "COREPL-XXXX"
commentBody: "<content in Markdown>"

Optional visibility restriction:

commentVisibility: {"type": "group", "value": "developers"}