Skip to main content

LINEAR-123: Complete Ticket Lifecycle Example

This example demonstrates a complete ticket lifecycle from start to finish, showing all Linear MCP interactions, progress updates, and status transitions.

Ticket Details

ID: LINEAR-123 Title: Add user authentication with OAuth2 Type: Feature Priority: High Status: Done Assignee: Backend Developer Agent Created: 2025-01-08 Completed: 2025-01-10

Phase 1: Ticket Start (Day 1 - Morning)

1. Fetch Ticket Details

Response:

2. Update Status to “In Progress”

3. Add Initial Comment with Implementation Plan


Phase 1 Complete (Day 1 - Afternoon)

4. Progress Update After Phase 1


Phase 2 Complete (Day 1 - Evening)

5. Technical Decision Documented

6. Phase 2 Progress Update


Blocker Encountered (Day 2 - Morning)

7. Blocker Reported

8. Update Status to Blocked


Blocker Resolved (Day 2 - Afternoon)

9. Blocker Resolution Update

10. Update Status Back to In Progress


Phase 3 Complete (Day 2 - Late Afternoon)

11. Phase 3 Progress Update


Phase 4 Complete (Day 2 - Evening)

12. Phase 4 Progress Update


Ready for Review (Day 2 - Evening)

13. Mark Ready for Review

14. Add Final Implementation Comment


Code Review Feedback (Day 3 - Morning)

15. Code Review Feedback Addressed


QA Testing Complete (Day 3 - Afternoon)

16. QA Approval


Deployment (Day 3 - Evening)

17. Deployment Complete


Summary

This ticket demonstrates a complete lifecycle including:
  1. Initial setup - Fetched ticket, updated status, created plan
  2. Progress tracking - Regular updates after each phase
  3. Technical decisions - Documented choice of Passport.js
  4. Blocker handling - Reported blocker, resolved, resumed work
  5. Code review - Addressed feedback, re-tested
  6. QA testing - Comprehensive testing by QA agent
  7. Deployment - Successful production deployment
  8. Completion - Final stats and metrics documented
Total Duration: 3 days Total Comments: 17 updates Status Transitions: Todo → In Progress → Blocked → In Progress → In Review → Done This example follows all best practices from the Linear Integration skill.