Features
Tickets & Task Management
The Tickets feature provides a full-featured task management system with Kanban boards and sprint planning. Track issues, assign work, and manage your team's workload all within PeerScripts.
Tickets & Task Management
The Tickets feature provides a full-featured task management system with Kanban boards and sprint planning. Track issues, assign work, and manage your team's workload all within PeerScripts.
Overview
Effective issue resolution requires tracking. The Tickets system provides:
- Kanban Board: Visual task management with drag-and-drop
- Sprint Planning: Organize work into time-boxed iterations
- Issue Integration: Create tickets directly from detected issues
- Team Assignment: Assign tasks to team members
- Progress Tracking: Monitor completion and velocity
Getting Started
Creating Your First Ticket
- Navigate to Tickets in the sidebar
- Click New Ticket
- Fill in ticket details:
- Title: Brief description of the task
- Description: Full details and context
- Priority: Low, Medium, High, or Critical
- Assignee: Team member responsible
- Due Date: Target completion date
- Click Create
From an Issue
Create tickets directly from detected issues:
- View any issue (Theme, Quality, Catalog, etc.)
- Click Create Ticket
- Issue details are pre-filled
- Adjust as needed
- Click Create
Kanban Board
Board Layout
┌─────────────────────────────────────────────────────────────────────────┐
│ KANBAN BOARD [+ New] [Sprint ▾] │
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ BACKLOG │ │ TODO │ │ IN PROGRESS │ │ DONE │ │
│ │ (8) │ │ (4) │ │ (3) │ │ (12) │ │
│ ├──────────────┤ ├──────────────┤ ├──────────────┤ ├──────────────┤ │
│ │ │ │ │ │ │ │ │ │
│ │ ┌──────────┐ │ │ ┌──────────┐ │ │ ┌──────────┐ │ │ ┌──────────┐ │ │
│ │ │Fix header│ │ │ │Update SEO│ │ │ │Optimize │ │ │ │Fixed XSS │ │ │
│ │ │navigation│ │ │ │meta tags │ │ │ │images │ │ │ │vulnerab. │ │ │
│ │ │ 🔴 High │ │ │ │ 🟡 Medium│ │ │ │ 🟡 Medium│ │ │ │ ✓ Complete│ │ │
│ │ │ @john │ │ │ │ @sarah │ │ │ │ @john │ │ │ │ @sarah │ │ │
│ │ └──────────┘ │ │ └──────────┘ │ │ └──────────┘ │ │ └──────────┘ │ │
│ │ │ │ │ │ │ │ │ │
│ │ ┌──────────┐ │ │ ┌──────────┐ │ │ ┌──────────┐ │ │ │ │
│ │ │Add lazy │ │ │ │Review │ │ │ │Fix cart │ │ │ ... │ │
│ │ │loading │ │ │ │discounts │ │ │ │bug │ │ │ │ │
│ │ │ 🔵 Low │ │ │ │ 🟡 Medium│ │ │ │ 🔴 High │ │ │ │ │
│ │ └──────────┘ │ │ └──────────┘ │ │ │ @john │ │ │ │ │
│ │ │ │ │ │ └──────────┘ │ │ │ │
│ │ ... │ │ ... │ │ │ │ │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘ │
└─────────────────────────────────────────────────────────────────────────┘
Moving Tickets
Drag and drop tickets between columns to update status:
- Backlog → Todo: Ready to start
- Todo → In Progress: Work begun
- In Progress → Done: Work complete
Or click a ticket and use the status dropdown.
Custom Statuses
Create custom columns for your workflow:
- Go to Settings > Tickets
- Click Manage Statuses
- Add, reorder, or remove statuses
- Changes apply immediately
Ticket Details
Viewing a Ticket
┌─────────────────────────────────────────────────────────────────┐
│ TICKET: Fix header navigation on mobile │
│ │
│ Status: In Progress Priority: 🔴 High │
│ Assignee: John Due: Jan 20, 2025 │
│ Created: Jan 15, 2025 Sprint: Sprint 12 │
│ │
│ ───────────────────────────────────────────────────────────── │
│ │
│ DESCRIPTION │
│ The mobile navigation menu is not expanding when tapped on │
│ iOS devices. This affects approximately 40% of our mobile │
│ traffic. │
│ │
│ Source: Theme Intelligence scan (Jan 14) │
│ Related Issue: JS error in header.liquid line 45 │
│ │
│ ───────────────────────────────────────────────────────────── │
│ │
│ TIME TRACKING │
│ Estimated: 4 hours │
│ Logged: 2.5 hours │
│ │
│ ───────────────────────────────────────────────────────────── │
│ │
│ NOTES (3) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ John (2h ago): Found the issue - event listener not │ │
│ │ binding correctly. Working on fix. │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │
│ [Edit] [Add Note] [Log Time] [View Source Issue] │
└─────────────────────────────────────────────────────────────────┘
Ticket Properties
| Property | Description |
|---|---|
| Title | Brief description |
| Description | Full details, context, acceptance criteria |
| Status | Current workflow state |
| Priority | Low, Medium, High, Critical |
| Assignee | Team member responsible |
| Due Date | Target completion |
| Sprint | Associated sprint (if any) |
| Estimated Hours | Planned effort |
| Logged Hours | Actual effort |
| Source | Where the ticket originated |
Sprint Planning
What Are Sprints?
Sprints are time-boxed periods (typically 1-2 weeks) for completing a set of tickets. They help with:
- Planning work capacity
- Tracking velocity
- Focusing efforts
- Measuring progress
Creating a Sprint
- Navigate to Tickets > Planning
- Click New Sprint
- Set sprint details:
- Name: Sprint 12, January Sprint, etc.
- Start Date: When work begins
- End Date: Sprint deadline
- Goal: What you want to accomplish
- Click Create
Sprint Planning View
┌─────────────────────────────────────────────────────────────────┐
│ SPRINT PLANNING │
│ │
│ Sprint 12: Jan 15 - Jan 29 │
│ Goal: Resolve all critical theme issues │
│ │
│ ┌─────────────────────────────────┬───────────────────────────┐│
│ │ BACKLOG │ SPRINT 12 ││
│ │ │ ││
│ │ ┌──────────────────────────┐ │ ┌──────────────────────┐ ││
│ │ │ Add lazy loading │──│──│ Fix header navigation│ ││
│ │ │ Est: 2h • @unassigned │ │ │ Est: 4h • @john │ ││
│ │ └──────────────────────────┘ │ └──────────────────────┘ ││
│ │ │ ││
│ │ ┌──────────────────────────┐ │ ┌──────────────────────┐ ││
│ │ │ Review old discounts │ │ │ Update SEO meta tags │ ││
│ │ │ Est: 3h • @sarah │ │ │ Est: 6h • @sarah │ ││
│ │ └──────────────────────────┘ │ └──────────────────────┘ ││
│ │ │ ││
│ │ ... more tickets │ ... more tickets ││
│ │ │ ││
│ ├─────────────────────────────────┼───────────────────────────┤│
│ │ Total: 45h estimated │ Total: 24h / 32h capacity││
│ └─────────────────────────────────┴───────────────────────────┘│
│ │
│ [Start Sprint] [Save] [Clear Sprint] │
└─────────────────────────────────────────────────────────────────┘
Managing Sprints
- Add tickets: Drag from backlog to sprint
- Remove tickets: Drag back to backlog
- Start sprint: Begin work, lock sprint contents
- Close sprint: Mark complete, move unfinished to backlog
Team Assignment
Assigning Tickets
- Open ticket details
- Click the Assignee field
- Select team member
- Save
Or drag a ticket to a team member's swim lane (if enabled).
Workload View
See tickets per team member:
┌─────────────────────────────────────────────────────────────────┐
│ TEAM WORKLOAD │
│ │
│ John (12h assigned) │
│ ████████████████░░░░░░░░ 75% of capacity │
│ ├─ Fix header navigation (4h) - In Progress │
│ ├─ Optimize images (4h) - In Progress │
│ └─ Fix cart bug (4h) - In Progress │
│ │
│ Sarah (8h assigned) │
│ ████████████░░░░░░░░░░░░ 50% of capacity │
│ ├─ Update SEO meta tags (6h) - Todo │
│ └─ Review discounts (2h) - Todo │
│ │
│ Unassigned (14h) │
│ ├─ Add lazy loading (2h) │
│ ├─ Fix mobile footer (4h) │
│ └─ ... 3 more tickets │
└─────────────────────────────────────────────────────────────────┘
Notes & Comments
Adding Notes
Add context, updates, or discussions to tickets:
- Open ticket details
- Click Add Note
- Enter your note
- Click Save
Notes are timestamped and attributed to the author.
Attachments
Attach files to tickets:
- Click Add Attachment
- Upload file or drag-and-drop
- File is linked to ticket
Supported: Images, PDFs, documents, code files
Time Tracking
Logging Time
Track effort on tickets:
- Open ticket
- Click Log Time
- Enter hours spent
- Add optional note
- Save
Time Reports
View time spent across tickets:
- By team member
- By sprint
- By priority
- By source (Theme issues, Quality issues, etc.)
Filtering & Search
Filter Options
| Filter | Options |
|---|---|
| Status | Backlog, Todo, In Progress, Done |
| Priority | Low, Medium, High, Critical |
| Assignee | Team members or Unassigned |
| Sprint | Active sprint, Backlog, Completed |
| Source | Theme, Quality, Catalog, Manual |
| Due Date | Overdue, This week, This month |
Search
Search tickets by:
- Title text
- Description content
- Ticket number (#123)
- Assignee name
Bulk Operations
Selecting Multiple Tickets
- Use checkboxes on ticket cards
- Or Shift+Click for range selection
- Selected count appears in toolbar
Bulk Actions
| Action | Description |
|---|---|
| Change Status | Move multiple tickets |
| Assign | Set assignee for all |
| Set Priority | Update priority |
| Add to Sprint | Include in sprint |
| Delete | Remove tickets |
Statistics & Reporting
Sprint Stats
┌─────────────────────────────────────────────────────────────────┐
│ SPRINT 12 STATISTICS │
│ │
│ Progress: [████████████████░░░░] 80% │
│ │
│ Tickets: Started: 15 Completed: 12 Remaining: 3 │
│ Story Points: Planned: 42 Completed: 34 Remaining: 8 │
│ Hours: Estimated: 32 Logged: 28 Remaining: 4 │
│ │
│ Burndown │
│ 40 │───╮ │
│ 30 │ ╰───╮ │
│ 20 │ ╰───╮ ╭─ Ideal │
│ 10 │ ╰────╯─ Actual │
│ 0 │ │
│ └─────────────────────── │
│ Day 1 5 10 14 │
└─────────────────────────────────────────────────────────────────┘
Velocity Tracking
Track completed work over sprints:
- Tickets completed per sprint
- Hours completed vs estimated
- Trends over time
Best Practices
Effective Tickets
- Clear titles - Specific and actionable
- Detailed descriptions - Include context and acceptance criteria
- Proper priority - Reserve Critical for true emergencies
- Realistic estimates - Better to overestimate
- Single responsibility - One task per ticket
Sprint Planning
- Capacity planning - Don't overcommit
- Buffer time - Leave room for unexpected work
- Priority ordering - Do high-priority first
- Daily standups - Review progress regularly
- Retrospectives - Learn from each sprint
Team Collaboration
- Assign everything - Clear ownership
- Update status - Move tickets promptly
- Add notes - Document decisions and progress
- Review regularly - Keep backlog groomed
Integration
From Detection Systems
Tickets integrate with all PeerScripts detection systems:
- Theme Intelligence issues
- Quality Audit findings
- Catalog Intelligence problems
- Store Health anomalies
- App Intelligence risks
Export & Reporting
Export ticket data:
- CSV for spreadsheets
- JSON for integrations
- PDF reports for stakeholders
Troubleshooting
Tickets Not Appearing
- Check filter settings
- Verify sprint selection
- Refresh the page
Can't Move Tickets
- Ensure you have edit permissions
- Check if sprint is locked
- Try clicking instead of dragging
Missing Team Members
- Team members must be added in Settings
- Check their permission level
Related Features
- Settings - Team management
- Action Center - Bulk issue resolution
- Store Health - Issue sources