Planning, Boards and Reports

This release strengthens the planning loop from roadmap to backlog, board, sprint, and report. You can plan with timelines, refine work in backlogs, run Kanban and Scrum boards, measure burndown, and inspect the background systems that keep Pomavo current.

Timeline roadmap with zoom and saved preferences

The Timeline view gives you a Gantt-style roadmap for work across weeks and months. Tickets are plotted across date ranges, sprint bars appear in the header, and dependency context helps you see scheduling risk earlier.

Timeline zoom is now user controlled. You can zoom out for a long roadmap or zoom in for day-level detail. Pomavo saves the zoom level in user preferences with a short debounce, so your next visit opens at the scale you chose.

The timeline also calculates a useful range even when a project has little scheduled data. It includes dynamic buffer days based on sprint duration and extends far enough into the future for longer-term planning.

Backlog refinements for grooming and prioritization

The Backlog view is the flat planning surface for upcoming work. You can sort, filter, drag, edit, and bulk-select tickets before they move into delivery.

Backlog grooming is where the team turns intake into ready work. Pomavo supports that by letting you review new items, estimate effort, set priority, move ready items into the current sprint, and archive or close stale work.

Effort-based sorting fits naturally here. If your templates include an Effort number field or mapped dropdown estimates, the backlog can help you discuss size and order without switching to reports.

Kanban refinements for continuous flow

The Kanban board gives continuous delivery teams a live view of work moving through workflow states. Columns map to states, cards move as work progresses, and WIP limits help prevent overload.

You can hide workflow states that do not need board visibility, reorder columns to match the team's process, and enable swimlanes for a second layer of organization.

Swimlanes are especially useful when one board mixes bugs, tasks, and incidents. You keep the same workflow columns while separating work by type, owner, or priority.

Scrum boards, dynamic sprints, and sprint restart

The Scrum board organizes work into time-boxed iterations. You can create sprints, define start and end dates, plan by dragging backlog items into a sprint, work through an active sprint board, complete sprints, and track burndown.

Sprint actions now support richer lifecycle management. You can start a sprint, complete a sprint, restart a sprint, move incomplete items back to the backlog while completing, or carry incomplete items into the next planned sprint.

Dynamic sprint planning also respects project sprint duration. The timeline and board calculations can use configured sprint length, with 14 days as the default when no project-specific value is set.

Configurable estimates and effort-based sorting

Estimation is configurable rather than hard-coded. Boards can override template fields for effort estimation and map dropdown values to numeric estimates, such as mapping T-shirt sizes to story points.

This gives teams flexibility. One project can use a numeric Effort field, another can use Story Points, and another can map values such as Small, Medium, Large, and Extra Large to numbers for burndown.

Effort-based ticket sorting makes planning conversations clearer. You can bring high-effort work into view, balance a sprint before starting, and spot large tickets that may need splitting.

Swimlanes across boards and backlogs

Swimlanes give you another dimension on top of a list or board. Pomavo supports grouping by template type, assignee, or priority on boards, with backlog swimlane organization for dense planning views.

Swimlanes help teams keep focus without creating separate boards for every concern. You can view the same tickets through a different organizational lens while preserving workflow columns and rank.

Unified burndown and report system

Pomavo now connects board estimates to reporting. Reports include a Sprint Burndown report that tracks remaining work across a sprint, compares ideal and actual burn rate, and visualizes scope change.

The Report Pane brings analytics into the project view as a collapsible panel. You can open it beside a board to review real-time metrics without losing board context.

The Report Page is documented as a planned full-page dashboard. Planned capabilities include custom layouts, cross-project reporting, date range selectors, CSV or PDF export, and scheduled report emails.

Saved queries connect search to planning

Saved Queries remain personal shortcuts, but they are especially powerful in planning workflows. You can save queries for sprint candidates, stale work, unassigned high-priority tickets, or recently completed items.

1
2

status not in ("Done", "Closed") and "Effort" >= 8
order by "Effort" desc, priority desc

1
2
3

assignee = @me and status = "In Review"
order by updated_at asc
limit 20

Saved queries can auto-refresh from 5 seconds to 15 minutes. That makes them useful as lightweight planning dashboards, triage queues, and personal work views.

Because the same DSL supports grouping and projection, saved queries can also power summary-style analysis before a full report is needed.

1
2
3
4

status != "Done"
group by assignee
return assignee, count() as open_tickets, sum(
quot;Effort") as effort
order by effort desc

Background jobs and admin visibility

The Admin Dashboard gives operators a view into Pomavo's background systems. It is designed for platform administrators and on-call engineers, not everyday project users.

Pomavo runs side effects as asynchronous background jobs. Automation evaluations, search indexing, history recording, inbox delivery, and scheduler resumes can be processed without blocking user-facing requests.

This release connects planning, execution, measurement, and operations. The timeline helps you plan dates, backlog and boards help you sequence work, sprint tools help you run iterations, reports show progress, saved queries keep important work visible, and the admin dashboard helps operators verify that background processing is healthy.