Roadmap and delivery targets

Every roadmap is fiction until the period ends. Hydrant’s version at least keeps the receipts: you say when you intend to deliver something, and when the period closes, it tells you what shipped, what moved and what quietly didn’t.

Before you start

Anyone in the workspace can open Roadmap and set or change an issue’s target.
Admins and the Owner set targets on projects and milestones, and confirm the planning calendar. Who can do what.
Targets work straight away. Period reviews need a confirmed planning calendar first (below).

Steps

Know what a target is

A delivery target is when you intend to deliver something: a year, a quarter or a month. That’s all it is.

It’s not a deadline. Nothing turns red or nags anyone.
It’s not a cycle. Cycles schedule the next few weeks of work; targets say which period something should land in. They’re independent.
It’s not priority, and it’s not snooze. An issue targeted for next quarter still shows up today. To hide it until later, snooze it.

Each project, milestone and issue has at most one target, and it’s optional. Targets don’t inherit. An issue in a project targeted for Q3 is not itself targeted for Q3, and changing the project’s target never rewrites anything inside it. Where a containing project or milestone has a target, Hydrant shows it beside the item’s own target as context, labelled Project or Milestone.

Confirm the planning calendar

Periods start and end at midnight somewhere. Pick where, once.

An Admin opens Settings › Calendar (or Confirm a calendar on the Roadmap).
Choose the Planning timezone, a named zone like America/Chicago. Hydrant suggests yours.
Check the ruler at the top of the page: its Planning row shows where each month and the next quarter start in that zone. Then click Confirm planning calendar.

This timezone sets period boundaries for Roadmap, Insights and the days in the Projects activity strip. Cycle schedules and personal snoozes keep their own timezones. Changing it later (Change planning timezone) only affects current and future reviews; past reviews keep the timezone that applied when their period started. Calendar history lists every change and who made it.

Set a target

Click the target chip on an issue’s Target row, in a project’s header, on a milestone, or on any Roadmap row.
In Delivery target, choose Year, Quarter or Month, then the period. “Know the quarter? Use the quarter.” Don’t claim a month you can’t name.
Optionally open Add a reason and fill in What changed?.
Click Set target (or Save target when changing one).

The dialog tells you what kind of change you’re making: set, narrowed, broadened, brought forward or deferred. A deferral is labelled honestly: “This changes the target, not delivery status.” Clear target removes it, and the old one “stays in the receipts”. Planning history in the same dialog shows every earlier target. You can target a period that has already ended; the review will say so.

Read the Roadmap

Open Roadmap in the sidebar. Periods with anything targeted are listed in order, each with counts of projects, milestones and issues, a date range and a Past, Current or Upcoming tag. The current period opens by default. Inside, each period has three lanes: Projects (outcomes), Milestones and issues.

The toolbar changes what you see. Jump to focuses one period. Display holds the rest, and shows a dot when either differs from the default; Reset puts both back:

Target match: Contained (default) folds narrower targets into wider ones: a quarter includes its months, a year includes its quarters and months, each counted once. Exact shows only items targeted at exactly that period.
Issues: Standalone only (default) lists issues that aren’t in a project, because project work has its own lane. Including project work lists them all.

Rows flag trouble: an issue that depends on a blocker targeted later, a blocker with no target at all, or an item targeted later than its project or milestone. Whenever at the bottom links to everything without a target.

Move several issues at once

Tick issues in a period, click Move N issues…, choose the new period and an optional reason, then confirm. Only the selected issues change; their projects, milestones and sub-issues keep their own targets. Hydrant applies them one by one and shows which succeeded. If one can’t be confirmed, Retry the original command resends exactly the same change.

Review a period

Focus a period with Jump to or Focus and review, then click Review period. Set Cutoff to Period end or Now.

The review counts projects, milestones and leaf issues separately. It splits each into:

Opening scope: what was targeted at this period when it started.
Added later: what was targeted after it started.

Each item ends up Delivered, Moved, Canceled, Cleared or Unfinished. The opening scope never shrinks. Deferring, clearing, canceling or trashing an item doesn’t remove it from the count. “Moving the date isn’t shipping.” Something delivered after the period ended is shown as late. Something already delivered before the period opened doesn’t count as this period’s delivery.

What you should see

A Roadmap where each period says, in plain numbers, how much is aimed at it. After a period ends, its review reads something like “Four delivered. Two moved. One canceled. One still open.” Parent issues appear as context and aren’t counted, so a parent and its children don’t count twice.

If it goes sideways

“No planning calendar yet.” Targets work; reviews wait for an Admin to confirm the timezone under Settings › Calendar.
“Planning history is incomplete.” The period started before Hydrant was recording targets, so its opening scope before that point is unknown. Hydrant says so instead of guessing.
You can’t change a project or milestone target. That needs an Admin or the Owner. Issue targets don’t.
An issue isn’t in its project’s period. Targets don’t inherit. Give the issue its own target, or set Display › Issues to Including project work to see it in the project lane.
A period shows only the first 100 rows. Use Open in issues to see the full list with a filter.
“Save not confirmed. Check the current target before retrying the original change.” The save may or may not have landed. Open the target, check it, then retry.

Timeline view

Use Timeline to compare current project and milestone delivery windows across twelve months. Periods remains the default and includes issues and period reviews. The timeline starts at the previous quarter in the workspace planning calendar; move forward a quarter or return with Current window (on narrower pages it is a calendar icon button with the same name).

Expand a project to see its milestones, including untargeted milestones as context. A project can appear because a milestone has a target even when the project itself does not. Long targets clip at the visible boundary; arrows indicate continuation, not a changed target. Select a target to use the same target editor as Periods.

Progress counts completed leaf issues and excludes canceled issues from the denominator. Canceled counts appear separately. Status and progress describe current work, not historical delivery; Done does not mean in production. Bands represent delivery windows, never work start dates or durations.

Use Find a project… to search project names; search waits briefly while you type. Add Filter › State to show projects in one state; it does not change their milestones’ own states. Set Display › Ordering to Target soonest (the default, by the earliest overlapping project or milestone target), Name · A–Z or Most complete first. Empty and canceled-only scopes sort last by completion. Display shows a dot while the ordering is not the default, and Reset restores it. Clear removes the search and the state; window navigation keeps those choices. Timeline controls do not alter Periods’ filters or review selection.