Issue Lifecycle
Standard lifecycle for tasks, bugs, and change requests across the FitZalo V2 project.
Task States
State Definitions
| State | Description | Who Owns | Exit Criteria |
|---|---|---|---|
TODO | Task defined, not started | — | Assigned to developer |
DOING | Actively being worked on | Dev | PR submitted |
IN_REVIEW | Code review in progress | Reviewer | PR approved or changes requested |
QA | Testing by QA or automated tests | QA | All tests pass |
BLOCKED | Cannot proceed due to dependency | Dev → escalate to PM | Blocker resolved |
DONE | Merged to main, tested, deployed | — | DoD met |
CANCELLED | Removed from scope | PM/PO | Decision logged |
Issue Types
| Type | Prefix | Description | SLA |
|---|---|---|---|
SPEC | V2-MOD-SPEC-NNN | Specification / behavior doc | Before coding |
BE | V2-MOD-BE-NNN | Backend implementation | Sprint-bound |
FE | V2-MOD-FE-NNN | Frontend implementation | Sprint-bound |
QA | V2-MOD-QA-NNN | Test creation / execution | Before release |
DEVOPS | V2-MOD-DO-NNN | Infrastructure / CI/CD | Before deploy |
DOC | V2-MOD-DOC-NNN | Documentation | Before handoff |
BUG | V2-MOD-BUG-NNN | Defect fix | Based on severity |
Bug Severity
| Severity | Response SLA | Fix SLA | Example |
|---|---|---|---|
| P0 Critical | 1 hour | 4 hours | Login broken, data loss |
| P1 High | 4 hours | 1 day | Feature not working, wrong data |
| P2 Medium | 1 day | 1 sprint | UI glitch, minor logic error |
| P3 Low | 3 days | Backlog | Cosmetic, typo, enhancement |
Transitions & Responsibilities
| Transition | Action | By | Notification |
|---|---|---|---|
| TODO → DOING | Assign self / pick from board | Dev | Board update |
| DOING → IN_REVIEW | Create PR, link task | Dev | Reviewer tagged |
| IN_REVIEW → DOING | Request changes on PR | Reviewer | Dev notified |
| IN_REVIEW → QA | Approve PR, merge | Reviewer | QA notified |
| QA → DONE | All tests pass | QA | PM notified |
| QA → DOING | Test failure logged | QA | Dev notified with repro |
| ANY → BLOCKED | Log blocker reason + dependency | Dev | PM escalated |
| BLOCKED → DOING | Blocker resolved | PM/Dev | Resume work |
Escalation Path
Dev (stuck > 2h) → Tech Lead → Architect (design issue) → PM (scope/priority)Sprint Ceremonies
| Ceremony | Frequency | Duration | Participants |
|---|---|---|---|
| Daily standup | Daily | 15 min | Dev team |
| Sprint planning | Bi-weekly | 1 hour | Dev + PM + PO |
| Sprint review | Bi-weekly | 30 min | All stakeholders |
| Retrospective | Bi-weekly | 30 min | Dev team |
| Module handoff | Per module completion | 1 hour | Dev + QA + TL |