Product Roadmap
What TATER is building, what stage each item has reached, and roughly when we expect it — with the ability to follow the ones you care about and be told when they move.
What it is
My TATER → Personal → Product Roadmap is the customer-facing view of what is coming. It is the same list for every customer — it is platform content, not something your organization configures — and it is maintained by TATER Security from the internal engineering board, so it moves as the work moves rather than being rewritten by hand at release time.
There is also a shortcut button for it in the My TATER topbar, so you can check it without navigating away from whatever you were doing.
Target quarters are estimates, not commitments
This is the single most important thing to understand about the page, and it is stated on the page itself for the same reason.
A target quarter is a working estimate typed by whoever owns the item. It reflects genuine intent at the moment it was written, and it moves — scope changes, a security issue jumps the queue, a dependency slips. Treating a quarter as a delivery date means treating an ordinary re-plan as a broken promise, which is the wrong reading of what is on the page. If a date genuinely matters to a decision you are making, ask us rather than inferring it from a lane.
The five status lanes
Every item sits in exactly one status, and you can filter to one from the Any status dropdown:
| Status | What it means |
|---|---|
| Planned | Committed to as a direction and scoped enough to describe. Nobody is writing code yet, and the target quarter here is the softest of any lane. |
| In development | Actively being built. The shape is settled; the delivery date is the thing still in motion. |
| Rolling out | Built and shipping progressively — typically behind a flag, to some organizations before others. If an item is in this lane and you do not see the feature yet, that is expected rather than a fault. |
| Launched | Generally available. Items stay visible in this lane for a while rather than disappearing, so you can see what recently landed. |
| Cancelled | Not being built. Shown deliberately rather than deleted — if you followed something, you are owed the answer, and a silently vanished item is worse than a clear "no". |
Finding what is relevant to you
- Product area narrows to one part of the platform — Endpoint, Compliance, and so on. The list of areas is built from what is actually on the roadmap right now rather than from a fixed list, so it never offers you a filter that matches nothing.
- Any status narrows to one lane. Pair it with an area to answer "what is being built for Endpoint right now".
- Following only hides everything except the items you follow — the fastest way to turn a long roadmap into your own short list.
Following an item
Click Follow on any item to be told when it changes status. This is the point of the page: rather than checking back, you subscribe once and hear about the handful of things you care about.
What to expect:
- You are notified on status changes — planned to in-development, in-development to rolling out, and so on. Notifications carry both the new status and the one it moved from, so "it moved" is never the whole message.
- Cancellation notifies too. An item you followed being cancelled is exactly the case where you need to know.
- Following is per person, not per organization. Your colleagues do not inherit your follows, and unfollowing affects only you.
- Every notification carries an unsubscribe link, and your organization's notification preferences apply to these the same as to any other TATER mail.
Use Following only to review what you have subscribed to; unfollow from the same button you followed with.
Authoring the roadmap (TATER Security staff)
This section does not apply to customers — the page it describes is SuperAdmin-only and lives in TATER Security → Settings → Product Roadmap.
Entries are drafted from the internal engineering board and published from there. Two properties of the model are worth knowing if you maintain it:
- Draft, published and archived are separate from the five status lanes. Status is where an item is in its lifecycle; publish state is whether customers can see it at all. An item can be in development for weeks as a draft before anyone outside sees it.
- Roadmap content is platform-wide, not per-organization. It is authored in the TATER Security tenant and read by every customer, so it never carries an organization id — a change published here is visible to everyone at once.
Because a status change fans out to every follower, treat publishing a change as sending mail, because it is.
Related
- My TATER for end users — the rest of the personal workspace.
- Notification Hub — how notification delivery and preferences work platform-wide.
- Release Management — for tracking your own releases inside TATER, which is a different thing from this page.
TATER