Issues
Issues (also called tickets) are the individual work items in your sprint. SprintFlint provides a kanban board for visualising and managing your issues.
Creating Issues
To create a new issue:
- Navigate to a sprint
- Click "New Issue" or the + button on any column
- Enter a title and description
- Set story points (optional but recommended)
- Click "Create Issue"
Issue Fields
| Field | Description |
|---|---|
| Title | Brief description of the work |
| Description | Detailed explanation, acceptance criteria, etc. |
| Story Points | Effort estimate (typically 1, 2, 3, 5, 8, 13) |
| Status | Current state: Backlog, To Do, In Progress, In Review, Done, Cancelled |
| Assignee | Team member responsible for the issue |
| Tags | Labels for categorisation (bug, feature, etc.) |
Issue Status
Issues move through different statuses as work progresses:
| Status | Description |
|---|---|
| Backlog | Not yet started, lower priority |
| To Do | Ready to be worked on |
| In Progress | Currently being worked on |
| In Review | Work complete, awaiting review |
| Done | Completed and verified |
| Cancelled | No longer needed |
Kanban Board
The kanban board provides a visual overview of your sprint. Each column represents a status, and issues are displayed as cards.
Moving Issues
You can move issues between columns by:
- Drag and drop - Drag the card to a different column
- Status dropdown - Click the issue and change the status
Real-Time Updates
The kanban board updates in real-time. When a team member moves an issue, you'll see the change instantly without refreshing the page.
Story Points
Story points are a relative measure of effort. Common scales include:
- Fibonacci - 1, 2, 3, 5, 8, 13, 21
- T-shirt sizes - XS=1, S=2, M=3, L=5, XL=8
Estimation Tip - Focus on relative complexity rather than time. A 2-point issue should be roughly twice the effort of a 1-point issue.
Tags
Tags help categorise issues. Common tags include:
- bug - Something isn't working correctly
- feature - New functionality
- enhancement - Improvement to existing feature
- documentation - Documentation updates
- tech-debt - Technical cleanup
You can create custom tags in your organisation settings.
Comments
Each issue has a comments section for discussion. Comments support:
- Rich text formatting
- File attachments
- @mentions to notify team members
Activity History
Every issue maintains an activity log showing:
- Status changes
- Assignee changes
- Story point updates
- Comments added
Issue Numbers
If your project has a prefix configured (e.g., "PROJ"), issues are automatically numbered like PROJ-1, PROJ-2, etc. These numbers are:
- Unique within the project
- Used for GitHub PR linking
- Searchable across the organisation
Next Steps
- GitHub Integration - Link pull requests to issues
- Autoplay - Let AI implement issues automatically