Skill: Jira Task Management

Purpose

Create, update, and track implementation tasks within stories.

When to Use

• Senior Developer breaks down stories into tasks
• Developers update task status
• Tracking progress on implementation

MCP Tools Used

Tool	Purpose
Atlassian:createJiraIssue	Create tasks
Atlassian:editJiraIssue	Update task details
Atlassian:transitionJiraIssue	Move through workflow
Atlassian:addCommentToJiraIssue	Add progress notes
Atlassian:getTransitionsForJiraIssue	Get available status transitions

Configuration

{
  "cloudId": "{{jira.cloudId}}",
  "projectKey": "{{jira.development.projectKey}}",
  "issueTypes": {
    "task": "{{jira.development.issueTypes.task}}",
    "subtask": "{{jira.development.issueTypes.subtask}}"
  }
}

Creating a Task

Task Format

## Description
[What needs to be done]

## Implementation Notes
- [Technical detail 1]
- [Technical detail 2]

## Files to Modify
- `path/to/file1`
- `path/to/file2`

## Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] Unit tests written
- [ ] Code documented

## Estimate
[X hours or story points]

Example: Create Task

Atlassian:createJiraIssue({
  cloudId: "{{jira.cloudId}}",
  projectKey: "{{jira.development.projectKey}}",
  issueTypeName: "Task",
  summary: "Implement password reset API endpoint",
  description: `## Description
Create the POST /api/auth/reset-password endpoint that initiates the password reset flow.

## Implementation Notes
- Use existing EmailService for sending
- Generate secure token with 24h expiry
- Rate limit to 3 requests per email per hour
- Log all reset attempts for security audit

## Files to Modify
- \`src/Controllers/AuthController.cs\`
- \`src/Services/PasswordResetService.cs\` (new)
- \`src/Services/EmailService.cs\`

## Acceptance Criteria
- [ ] Endpoint accepts email in request body
- [ ] Returns 200 OK regardless of email existence (security)
- [ ] Sends email if account exists
- [ ] Rate limiting works correctly
- [ ] Unit tests cover all scenarios
- [ ] Integration test for full flow

## Estimate
3 hours`,
  labels: ["agent-generated"],
  parent: { key: "MDDEV-45" }  // Link to parent story
})

Transitioning Task Status

// First, get available transitions
const transitions = await Atlassian:getTransitionsForJiraIssue({
  cloudId: "{{jira.cloudId}}",
  issueIdOrKey: "MDDEV-46"
});

// Then transition
Atlassian:transitionJiraIssue({
  cloudId: "{{jira.cloudId}}",
  issueIdOrKey: "MDDEV-46",
  transition: { id: "21" }  // ID from transitions response
})

Updating Task Progress

Atlassian:addCommentToJiraIssue({
  cloudId: "{{jira.cloudId}}",
  issueIdOrKey: "MDDEV-46",
  commentBody: `🤖 **Junior Developer Agent**

**Progress Update:**

✅ Endpoint created
✅ Token generation working
✅ Email service integration complete
🔄 Working on rate limiting
⬜ Unit tests pending

**Blockers:** None

**ETA:** Will complete today`
})

Used By Agents

• Senior Developer - Creates tasks from stories, assigns work
• Junior Developer - Updates progress, completes tasks
• Project Manager - Tracks task status