openmasu
solutions · product
Roadmap, requests and releases, connected in one base.
Lay out the roadmap on a timeline, collect feature requests through a public form and link each one to the feature it asks for. Group features into releases and plan launch tasks on a Gantt with dependencies.
- Roadmap timeline from start to end date
- Public request form, linked to features
- Gantt chart for launch tasks and dependencies
| Feature | Release | Start | End | Requests | Status |
|---|---|---|---|---|---|
| Bulk edit in grid | v2.4 | Apr 1 | Apr 18 | Edit many rows Paste ranges | In progress |
| Dark mode | v2.4 | Apr 8 | Apr 25 | Dark theme please | Planned |
| CSV export per view | v2.5 | May 2 | May 16 | Export filtered rows | Planned |
| Faster search | v2.3 | Mar 3 | Mar 21 | Search is slow | Shipped |
| Saved filters sharing | v2.5 | May 12 | Jun 6 | Share my filter | Exploring |
Everyday workflows
A roadmap on a timeline
Each feature has a «Start» and «End» date, a «Status» and a link to its release. The timeline view draws the quarter as bars, so overlaps and gaps are obvious. Keep a second view filtered to «Status is In progress» for the weekly product sync.
Feature requests from a public form
Share a form with support, sales or customers. Each answer arrives in «Requests» as a new record, live. During triage, link the request to an existing feature or create a new one; the feature's inverse field lists every request behind it, so demand is visible when you prioritize.
Releases that know what's in them
«Releases» holds the version, target date and notes. Link features to a release and open it to see its full scope. Use a list view grouped by release and status to write release notes from what actually shipped.
Launch tasks on a Gantt
Docs, QA, the announcement post and the support update are tasks with dates and dependencies on a Gantt chart. A formula IF(IS_BEFORE({Due}, TODAY()), "Overdue", "") flags anything slipping, and @mentions in comments pull in the right person.
Views & structure
Key views
- Timeline Show features from start to end date to plan the quarter.
- Form Let anyone submit a feature request without access to the base.
- Gantt Plan launch tasks with dependencies so blockers are visible.
- Kanban Triage requests from New to Linked, Declined or Done.
- List Nest features under releases and status for release notes.
Recommended fields
- Start / End (Date) Two dates that place each feature on the timeline.
- Release (Link to another record) Puts the feature in a release; the release lists its scope.
- Requests (Link to another record) Connects incoming requests to the feature they ask for.
- Impact (Rating) A 1 to 5 score to compare features during prioritization.
- Area (Multiple select) Tags like Editor, Search or Billing to filter the roadmap.
- Spec (URL) Links to the spec or design file wherever it lives.
Your agent over MCP
Connect your own agent (Claude, ChatGPT, Codex or Cursor) over MCP. It can triage new requests, link them to the right feature, count demand by area and draft launch tasks, all with your token's permissions and visible in history.
query_records link_records aggregate_records create_records update_records
Bring your roadmap and requests together
Start with Features, Requests and Releases, then share the request form with your team.