Plan a roadmap and cycles

The roadmap holds the work your team has chosen to do. Security findings, accepted feature ideas, and moderated community requests can all lead to private work items. They keep their source links so the reason for the work stays visible.

Create a useful work item

Open Roadmap → New work item. Give it an outcome and acceptance criteria, choose a type, and set the priority. You can also assign a teammate, add labels and an estimate, choose a target date, and put it in a planned or active cycle.

Types are feature, security, architecture, improvement, and bug. Priorities run from Urgent through High, Normal, Low, and No priority. Public vote counts are a separate signal; they never change priority automatically.

Use table view to compare fields or board view to group work by status. Open an item to edit it. Search, filters, sort order, selected work, and the view are saved in the URL, so a teammate can open the same context. Large lists load in pages; a board represents the records loaded so far.

Plan with community votes

Choose Most votes in the roadmap's sort control, or follow Plan with community votes from Community. Hyperoru ranks the entire filtered project by stored votes before loading a page. Equal counts follow the team's priority and then the work item number. Work with no votes remains in the list, including private security and architecture tasks.

This changes the view, not an item's priority, delivery state, or cycle. Your team still decides how demand, risk, dependencies, and effort shape the next release. Votes collected before a feature is withdrawn remain available for private planning; its vote count is labeled Private and its public copy stays withdrawn.

Vote totals can change while you browse. Choose Refresh votes to update the order. Pagination keeps the last displayed position when that item's votes or priority change, but an item that gains votes can move ahead of that position. Refresh to see the current complete ranking. Filters and the selected sort stay in the URL.

Make dependencies explicit

In Blocked by, choose work from the same project. Hyperoru rejects self-dependencies, circular chains, and references to another project. A dependent item cannot be marked done while its blockers remain unresolved. Reopening a blocker also requires you to reconcile any completed dependents first.

Done is a delivery state. It does not close a security finding or prove an architectural guardrail. Run a later source review to verify the system after the change.

Give a cycle a purpose

Open Cycles → Plan a cycle, then choose a goal and dates. Assign roadmap work to it. Cycle dates cannot overlap within a project, and only one cycle can be active. A future cycle can be planned now and started when its start date arrives.

Current & upcoming shows the active cycle first, followed by planned cycles in start-date order. History shows completed and canceled cycles, most recent first. The selected view stays in the URL. Load more cycles to continue through either list; choose Refresh cycles after another teammate changes the plan.

Assignment and rollover choices load open cycles independently of the visible cycle list. Use Load more open cycles to reach later plans. When editing retained work, its current closed cycle remains named and selected; loading options never removes an existing assignment.

Progress shows completed work and completed estimate points. Canceled work stays part of the original scope so it does not artificially improve completion.

Finish deliberately

Choose Finish cycle. If work remains unfinished, select another planned or active cycle, or return it to the backlog outside a cycle. This choice is required; unfinished work is never silently discarded.

The completed cycle retains its scope totals, completed count, estimates, and number of carried items. Its historical progress remains stable after rollover. View retained work opens items still assigned to that cycle; View destination cycle follows the selected rollover destination. Closed cycles cannot receive newly opened work. Canceling a cycle also preserves work and requires an explicit destination for unfinished items.

You can clarify a completed work item's title or description while retaining its closed-cycle assignment. To reopen that work, move it to an open cycle or choose No cycle in the same edit. The closed cycle's recorded completion totals remain unchanged.

Continue with community feature voting or the project agent.