jira-workflow

Jira Workflow Skill

Manage development workflows using Jira tickets. Supports four core operations: listing work, creating work, assigning work, and doing work.

Prerequisites

• Access to Jira via MCP Atlassian tools
• Git repository in the current workspace
• Appropriate Jira project permissions

Quick Reference

User Intent	Workflow
"List my work" / "Show my tickets"	→ List Work
"Create a ticket" / "Add work"	→ Create Work
"Assign PROJ-123 to John"	→ Assign Work
"Add label to PROJ-123"	→ Manage Labels
"List components"	→ List Components
"Do work" / "Work on PROJ-123"	→ Do Work

List Work

Display the user's assigned Jira tickets.

Steps:

1. Get the Atlassian Cloud ID using mcp_atlassian-mcp_getAccessibleAtlassianResources
2. Get current user info using mcp_atlassian-mcp_atlassianUserInfo
3. Search for issues assigned to current user using the search tools (activate with activate_search_tools_for_jira_and_confluence)
4. Present tickets in a clear table format

Output format:

| Key | Summary | Status | Priority |
|-----|---------|--------|----------|
| PROJ-123 | Implement login | In Progress | High |
| PROJ-124 | Fix date bug | To Do | Medium |

Create Work

Create a new Jira ticket.

Required information (prompt user if missing):

• Project key (or help user find it via mcp_atlassian-mcp_getVisibleJiraProjects)
• Summary (ticket title)
• Issue type (Story, Bug, Task, etc.)
• Component (see List Components for available options)

Mandatory fields (auto-populated):

• Requested by (BU): Default to GLCP. User can override if needed.
• Labels: Always include created-by-github-copilot. User can add additional labels.

Optional information:

• Description
• Priority
• Assignee
• Additional labels

Steps:

1. Get Cloud ID if not cached
2. Gather required fields from user
3. If issue type unknown, fetch available types via issue metadata tools (activate with activate_jira_issue_management_tools)
4. Check user preferences file for last-used component (see User Preferences)
5. If no component provided and preference exists, suggest it; otherwise prompt user
6. Create issue using mcp_atlassian-mcp_createJiraIssue with additional_fields: