From aai-pm-jira
Provides patterns for syncing Jira ticket statuses with dev progress: update triggers, transitions, comment templates, and API usage. Useful for accurate sprint burndowns and velocity.
npx claudepluginhub bradtaylorsf/alphaagent-teamThis skill uses the workspace's default tool permissions.
This skill provides patterns for keeping Jira tickets synchronized with actual development progress, ensuring accurate tracking and reporting.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
This skill provides patterns for keeping Jira tickets synchronized with actual development progress, ensuring accurate tracking and reporting.
| Event | Status Change | Comment |
|---|---|---|
| Assigned to you | → In Progress (or keep Open) | Note approach |
| Started coding | → In Progress | Brief plan |
| PR created | → Code Review | Link to PR |
| PR approved | → Ready for QA (if applicable) | Note reviewer |
| Tests passed | → Done | Summary of changes |
| Blocked | Keep current + add Blocker flag | Blocker details |
| Unblocked | Remove Blocker flag | Resolution note |
To Do ─────────────────────────────────────────────────────┐
│ │
▼ │
In Progress ──► Code Review ──► QA ──► Done │
│ │ │ │
│ (blocked) │ │ │
▼ ▼ ▼ │
Blocked ────────────────────────────────────────────────────┘
(returns to previous status when unblocked)
To In Progress:
Starting implementation. Approach:
- [Key step 1]
- [Key step 2]
Estimated completion: [Date]
To Code Review:
PR ready for review: [PR Link]
Changes:
- [Summary of changes]
Testing done:
- [Tests written/run]
To Done:
Completed and merged. Changes:
- [Summary]
Tested by: [Who tested]
Deployed to: [Environment]
To Blocked:
⚠️ BLOCKED
Reason: [Clear explanation]
Blocked by: [PROJ-XXX] or [External dependency]
Impact: [What can't proceed]
Action needed: [What would unblock]
ETA to unblock: [If known]
// GET /rest/api/3/issue/{issueKey}/transitions
// Response includes available transitions with IDs
// POST /rest/api/3/issue/{issueKey}/transitions
{
"transition": {
"id": "21" // Get ID from available transitions
},
"update": {
"comment": [{
"add": {
"body": {
"type": "doc",
"version": 1,
"content": [{
"type": "paragraph",
"content": [{
"type": "text",
"text": "Starting implementation"
}]
}]
}
}
}]
}
}
// POST /rest/api/3/issue/{issueKey}/comment
{
"body": {
"type": "doc",
"version": 1,
"content": [{
"type": "paragraph",
"content": [{
"type": "text",
"text": "Progress update: Completed API endpoint"
}]
}]
}
}
// PUT /rest/api/3/issue/{issueKey}
{
"fields": {
"assignee": { "id": "user-id" },
"labels": ["in-progress", "backend"]
}
}
⚠️ BLOCKED
*Reason*: Waiting for design approval on new notification UI
*Blocked by*: [PROJ-456|PROJ-456] (Design: Notification Templates)
*Impact*: Cannot implement email templates without approved designs
*Action needed*: Design team to complete and approve PROJ-456
*ETA*: Expected by Friday based on design team's sprint
@designer - Please prioritize when possible
✅ UNBLOCKED
*Resolution*: Design approved in PROJ-456
*Next steps*: Resuming implementation, will complete by EOD tomorrow
For tickets in progress > 1 day:
📊 Progress Update - [Date]
*Completed*:
- [What was done]
*In Progress*:
- [What you're working on]
*Next*:
- [What's planned next]
*Blockers*: None / [Description]
*ETA*: On track for [Date]
For sprint reviews:
📋 Sprint Progress - PROJ-123
*Status*: 70% complete
*Completed*:
- ✅ Backend API endpoint
- ✅ Database migrations
- ✅ Unit tests
*Remaining*:
- ⏳ Frontend integration (in progress)
- 🔜 E2E tests
- 🔜 Documentation
*Risk*: Low - On track for completion this sprint
| Trigger | Action |
|---|---|
| PR opened | → Code Review |
| PR merged | → Done (or QA) |
| Branch created | → In Progress |
| Build failed | Add "build-failed" label |
| Deploy to staging | Add "on-staging" label |
# In commit message:
PROJ-123 #time 2h #comment Implemented notification service
# Transitions:
PROJ-123 #in-progress Starting work
PROJ-123 #done Completed implementation
# Multiple actions:
PROJ-123 #time 1h 30m #comment Added tests #done
Solution: Add retroactive comment with dates
Retroactive update:
- Started: [Date]
- Completed: [Date]
- Forgot to update status during work
Solution: Audit and correct
Status correction:
- Old status: In Progress
- New status: Done
- Reason: Work completed [Date], status update missed
Solution: Clear ownership in comments
@developer1 working on backend
@developer2 working on frontend
Updates:
- Backend: Complete
- Frontend: In progress, ETA tomorrow
| Status | Means |
|---|---|
| To Do | Not started, in backlog |
| In Progress | Actively being worked |
| Code Review | PR open, awaiting review |
| QA | Ready for testing |
| Done | Completed and verified |
| Blocked | Cannot proceed |
| Situation | Comment |
|---|---|
| Starting | Brief plan/approach |
| Progress | What's done/remaining |
| Blocked | Details + action needed |
| Completed | Summary + verification |
| Questions | Clear question + context |