Statuses
Statuses represent the stages of your development workflow. Learn how to create, customize, and manage statuses to effectively track and communicate progress.
Understanding statuses
What are statuses?
Statuses are workflow stages that issues move through during development:
- New Post: Initial submission
- Under Review: Being evaluated
- In Progress: Currently being worked on
- Implemented: Completed and released
- Rejected: Not planned for implementation
Why statuses matter
- Progress tracking: Visual representation of work
- User communication: Keep users informed
- Team coordination: Align team on priorities
- Roadmap display: Show what's coming next
Creating statuses
Basic status setup
- Go to Project Settings → Statuses
- Click "Create Status"
- Configure status details:
- Name: Clear, descriptive name
- Icon: Visual identifier
- Color: Distinctive color
- Order: Position in workflow
- Click "Create Status"
Status configuration options
- Default status: Set for new issues
- Show in roadmap: Display on public roadmap
- Publish to changelog: Auto-publish when reached
- Archived: Hide from active workflow
Status workflow
Typical workflow stages
- New Post → Initial submission
- Under Review → Evaluation phase
- In Progress → Development started
- Testing → Quality assurance
- Implemented → Released to users
Customizing workflow
- Add stages: Insert new statuses as needed
- Remove stages: Archive unused statuses
- Reorder: Arrange in logical sequence
- Rename: Use terminology familiar to users
Status settings
Display options
- Roadmap visibility: Control which statuses appear publicly
- Changelog publishing: Auto-publish completed items
- Default selection: Set initial status for new issues
- Order index: Arrange statuses in sequence
Advanced settings
- Color coding: Visual identification system
- Icon selection: Choose from icon library
- Archived status: Hide without deleting
- Custom fields: Add status-specific information
Managing statuses
Active statuses
- Edit: Modify name, color, icon, or settings
- Reorder: Change workflow position
- Archive: Hide from new issues
- Delete: Remove permanently
Archived statuses
- Restore: Bring back archived statuses
- View issues: See existing issues in archived statuses
- Data preservation: Maintain issue history
Best practices
Status design
- Keep it simple: 4-6 statuses work best
- Clear progression: Logical workflow sequence
- User-friendly: Use terminology users understand
- Consistent: Maintain naming conventions
Workflow management
- Regular updates: Keep statuses current
- Team alignment: Ensure everyone understands workflow
- User communication: Explain status meanings
- Process improvement: Refine based on experience
Visual design
- Color consistency: Use brand colors when possible
- Icon clarity: Choose recognizable icons
- Accessibility: Ensure color contrast compliance
- Mobile friendly: Test on different screen sizes
Status automation
Automatic transitions
- Time-based: Move statuses after time periods
- Condition-based: Trigger on specific events
- User-triggered: Manual status changes
- Integration-based: External system updates
Notification settings
- Status change alerts: Notify relevant parties
- Progress updates: Keep stakeholders informed
- Completion notifications: Alert when items are done
- Custom triggers: Set up specific notifications
Roadmap integration
Roadmap display
- Visible statuses: Control what appears publicly
- Column layout: Kanban-style organization
- Progress indication: Show development stages
- User expectations: Set realistic timelines
Changelog publishing
- Auto-publish: Automatically publish completed items
- Manual control: Override automatic publishing
- Release notes: Generate from status changes
- Version tracking: Link to specific releases
Next steps
- [Board settings] - Configure permissions
- [Categories] - Organize with categories
- [Branding] - Customize appearance