Project Board

Master agile project management with customizable workflows and sprint planning

Creating and Managing Tickets

Creating a Ticket

Click "+ New Ticket" and fill in:

  • Title: Clear, concise summary
  • Type: Story, Task, Bug, or Epic
  • Description: Detailed requirements or bug report
  • Priority: Critical, High, Medium, or Low
  • Assignee: Team member responsible
  • Estimate: Story points or hours
  • Sprint: Assign to current or future sprint
  • Labels: Add tags for categorization

Ticket Types

  • Story: User-facing feature or requirement
  • Task: Work item without direct user value
  • Bug: Defect or issue to be fixed
  • Epic: Large feature containing multiple stories

Board Views

Kanban Board

Visualize work in columns representing workflow stages:

  • To Do: Work ready to start
  • In Progress: Currently being worked on
  • In Review: Ready for code review or testing
  • Done: Completed work

Drag and drop tickets between columns to update status.

List View

See all tickets in a filterable, sortable table. Perfect for:

  • Bulk editing tickets
  • Searching by text or filters
  • Exporting ticket lists
  • Quick overview of all work items

Custom Statuses

Customize your workflow in Settings → Project Board. Add, remove, or rename status columns to match your team's process.

Sprint Planning

Creating a Sprint

Click "Create Sprint" and configure:

  • Name: e.g., "Sprint 24" or "Q1 Release Sprint"
  • Duration: Set start and end dates (typically 2 weeks)
  • Goal: What you aim to achieve
  • Capacity: Total story points or hours available

Sprint Backlog

Drag tickets from the product backlog into your sprint. Monitor capacity to avoid overcommitment. The system will warn you if you exceed planned capacity.

Daily Standups

Use the board during standup meetings to:

  • Review what was completed yesterday
  • Identify blockers
  • Plan today's work
  • Update ticket statuses in real-time

Sprint Analytics

Burndown Chart

Track remaining work over time. The chart shows:

  • Ideal burndown line (expected progress)
  • Actual burndown line (real progress)
  • Scope changes during sprint
  • Projected completion date

Velocity Tracking

View historical velocity to improve future sprint planning. See completed story points per sprint and rolling averages.

Sprint Report

At sprint end, generate a report showing:

  • Commitment vs. completion
  • Tickets added/removed during sprint
  • Blockers encountered
  • Team capacity utilization

Best Practices

  • Keep your backlog groomed and prioritized
  • Break large epics into smaller, manageable stories
  • Estimate tickets as a team using planning poker
  • Update ticket status daily to keep the board accurate
  • Use labels to track work across multiple dimensions
  • Link related tickets to maintain traceability
  • Review sprint velocity to improve planning accuracy
  • Hold retrospectives to continuously improve process