Ticket Types
Everia supports four ticket types. Choosing the right type keeps your board readable and your sprint reports meaningful.
| Field | Description |
|---|---|
| Story | A user-facing feature or requirement. Describes value delivered to the end user — e.g. "As a user, I can reset my password". |
| Task | Internal work without direct user value — infrastructure updates, refactoring, documentation, or tooling. |
| Bug | A defect or regression that needs fixing. Link it to the failed test case so QA can verify the fix in the next run. |
| Epic | A large initiative containing multiple stories. Shows a roll-up view of progress across child tickets. |
Creating a Ticket
Click + New Ticket in the toolbar or press C anywhere on the board. Fill in the details and save.
| Field | Options | Description |
|---|---|---|
| Title | Clear, concise summary of the work item | |
| Type | Story / Task / Bug / Epic | Determines the icon, label colour, and available fields |
| Description | Full requirements, acceptance criteria, or bug reproduction steps | |
| Priority | Low / Medium / High / Urgent | Controls visual prominence on the board — Urgent tickets are highlighted |
| Assignee | Team member responsible for delivering this ticket | |
| Estimate | Story points or hours — used in sprint capacity planning and velocity tracking | |
| Sprint | Assign to the current sprint backlog or a future sprint | |
| Space | Sub-area of the board — useful for separating work by team, component, or feature area | |
| Labels | Free-form tags for cross-cutting concerns (e.g. frontend, API, design) | |
| Linked test cases | Test cases that validate this ticket — enables full QA traceability | |
| Start / End date | Optional date range — used in timeline and workload views |
Board & List Views
Board view (Kanban)
The default view. Tickets are arranged in columns representing workflow stages. Drag and drop a ticket between columns to update its status instantly.
- Default columns: To Do, In Progress, In Review, Done.
- Add, rename, reorder, or remove columns in Settings → Project Board → Statuses.
- Collapse columns to hide finished work and keep focus on active items.
- Filter the board by assignee, priority, type, label, or sprint using the filter bar.
- Use Spaces to group columns by team, component, or feature area — switch between spaces from the board toolbar.
List view
A sortable, filterable table — ideal for bulk editing or reviewing the full backlog without the visual overhead of the board.
- Click any column header to sort by that field.
- Filter by assignee, priority, type, label, or sprint.
- Inline-edit title, priority, and assignee without opening the full ticket.
- Toggle between Board and List using the view switcher in the toolbar.
Sprint Planning
Creating a sprint
Open the Sprints panel
Click Sprints in the left sidebar. Active and past sprints are listed here.
Click + New Sprint
Give it a clear name (e.g. "Sprint 24"), set start and end dates, and write a one-line sprint goal.
Set team capacity
Enter the total story points or hours available for the sprint. Everia warns you when adding tickets would exceed capacity.
Populate the sprint backlog
Drag tickets from the product backlog into the sprint, or use Add to Sprint on any ticket. The list view is often faster for bulk assignment.
Start the sprint
Click Start Sprint to activate the burndown chart. Tickets can still be added mid-sprint but Everia records each scope change explicitly.
Running daily standups with the board
- Open the Board view filtered to the current sprint before the meeting.
- Walk through In Progress tickets — update statuses live during standup.
- Flag blockers by setting priority to Urgent and @mentioning the person who can unblock.
- Keep the sprint goal visible as a daily anchor for the team's focus.
Closing a sprint
When the sprint ends, click Close Sprint. Everia prompts you to move any incomplete tickets — push them to the next sprint or back to the backlog. A sprint report is generated automatically on close.
Sprint Analytics
Burndown chart
The burndown chart updates in real time as tickets are completed.
- Ideal line — the expected straight-line path from total capacity to zero by the end date.
- Actual line — real progress. Above the ideal line means you are behind schedule.
- Scope-change markers — vertical dashes showing when tickets were added or removed mid-sprint.
- Projected completion — extrapolates the current pace to show whether you will finish on time.
Velocity tracking
Velocity is the total story points completed per sprint. Everia tracks it across all historical sprints and calculates a rolling average.
- Use the rolling average as your default capacity estimate for the next sprint.
- A velocity drop usually signals scope creep, unplanned work, or team unavailability — the sprint report shows exactly what happened.
Sprint report
Generated automatically when you close a sprint. Includes:
- Commitment vs. completion — how many points were planned vs. delivered.
- Scope changes — every ticket added or removed after the sprint started.
- Blockers encountered — tickets that spent time marked as blocked.
- Team utilisation — per-person workload and completion rate.
Best Practices
Groom the backlog weekly
Spend 30 minutes each week reviewing, estimating, and prioritising the backlog so sprint planning sessions stay under an hour.
Break epics into stories
Epics spanning more than two sprints are impossible to track meaningfully. Decompose them into stories of 1–5 points each.
Estimate as a team
Lone estimates miss shared assumptions. Use a short synchronous session or planning poker — disagreement on estimates often reveals hidden complexity.
Update statuses daily
A board with stale statuses is worse than no board. Make moving tickets a daily habit, not a pre-standup scramble.
Link tests to every Story and Bug
Every Story and Bug should have at least one linked test case before it is marked Done. Use the Coverage view to find gaps before a release.
Run a retro every sprint
Use Everia's built-in Retrospectives feature at the end of every sprint. Velocity data means more when paired with a team conversation about why it changed.