Project Board

The default view. Tickets are arranged in columns representing workflow stages. Drag and drop a ticket between columns to update its status instantly.

• Columns are set by your project's template when it's created — fully customizable during setup or later.
• Add, rename, recolour, reorder, or remove columns anytime 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.

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, List, and Gantt using the view switcher in the toolbar.

A tree-and-timeline view for scheduling and dependency planning across the whole project, not just the current sprint.

• Zoom between week, month, and quarter scales — your choice is remembered per project.
• Drag a bar to move or resize it, or drag an unscheduled ticket straight onto the timeline to set its dates.
• Draw dependencies between tickets by dragging from one bar to another — supports all four dependency types plus lag, with a popover to confirm, edit, or delete.
• Critical path and slack are highlighted automatically as dependencies change.
• Parent tickets roll up their children's date ranges, with an overflow indicator when a child runs outside the parent's window.
• Filter by status, priority, or labels, and search to jump to a ticket — matches auto-expand their parent chain.
• A today line marks the current date, and the toolbar has an export action for sharing a snapshot.

• 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.

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.

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 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.

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.