Product Roadmap

The Roadmap page is your organisation's feedback board. Everyone on your team can submit feature requests or bug reports, vote on them, and follow their status as they move from idea to shipped feature.

You see the requests your own organisation submitted. Requests from other Alpha customers are not visible to you, and yours are not visible to them; only the ASRR team sees the whole board, so they can plan across all customers.

Open it from the Roadmap entry in the sidebar; it is available to every signed-in user.

It is also in the Alpha mobile app: More → Roadmap, or Settings → Roadmap & feedback. The mobile board carries the same requests, votes and comments as the web board.

Submitting a request

Click New request and describe what you need:

• Title: a short summary of the request
• Description: what you need, why, and for whom
• Type: Feature (something new), Improvement (make something existing better), or Bug (something is broken)

You can attach screenshots to the request itself — pick them with the paperclip, or paste them straight into the description with Ctrl+V.

Submitting automatically counts as your first vote. Every request gets a public number (e.g. FR-00042).

Voting

Every user has one vote per request. The board is sorted by votes, so what your team cares about most rises to the top. Click the vote button again to withdraw your vote.

Voting matters: when a request changes status you are notified, and the ASRR team weighs votes (and how many different organisations asked for the same thing) when planning.

Statuses

When a request you submitted or voted for changes status, you receive a notification that links straight to that request.

Approving delivered work

A request you submitted does not go straight to Done. Once we have built it, it moves to Awaiting approval and lands back with your organisation, so the last word on whether something is finished is yours rather than ours.

Open the request and you will see two buttons:

• Approve: closes the request as Done and records that your organisation signed it off.
• Send back: returns it to Under review and asks for a reason. That reason is posted on the request as a comment, so the objection stays with the request instead of getting lost in a chat or an email.

Anyone in the submitting organisation can approve or send back, not only the person who filed the request. The ASRR team cannot approve on your behalf; they can only close a request as a recorded override, which the board shows as such.

Opening a request

Clicking a card opens the request on its own page: the description and its attachments, the discussion thread, and a timeline of everything that has happened to it — when it was submitted, every status change, when it was linked to internal work, and when it was approved or sent back.

Because it is a real page it has its own address, so you can open it in a new tab, bookmark it, or share the link with a colleague. Notifications about a request link straight to it rather than to the board.

Approving delivered work

A request you submitted does not go straight to Done. Once we have built it, it moves to Awaiting approval and lands back with your organisation, so the last word on whether something is finished is yours rather than ours.

Open the request and you will see two buttons:

• Approve: closes the request as Done and records that your organisation signed it off.
• Send back: returns it to Under review and asks for a reason. That reason is posted on the request as a comment, so the objection stays with the request instead of getting lost in a chat or an email.

Anyone in the submitting organisation can approve or send back, not only the person who filed the request. Other organisations cannot: they see the status, but the decision belongs to whoever asked for it.

Comments

Each request has a discussion thread. Use it to add context, describe your use case, or +1 with specifics: "we need this for X" is far more useful than a bare vote. Everyone who can see the request sees the whole thread: your own organisation and the ASRR team, whose replies are marked with an ASRR team badge. You can delete your own comments.

Screenshots in a reply

A screenshot usually explains a bug faster than a paragraph does. Add one to a reply with the paperclip button, or simply paste it into the reply box with Ctrl+V; pasted images upload on the spot and appear as thumbnails under the reply. A reply may be nothing but a screenshot. Up to ten attachments per reply; images show inline, other files as a download link.

Filtering

Use the filter at the top of the page to switch between All requests (everything your organisation has submitted), requests from My organisation, and requests submitted by Mine (you personally).

In the mobile app

The mobile board groups requests by status (Awaiting approval, In progress, Planned, Under review, Submitted, Done, Declined) with the same three filters at the top. Tap a request to read it, vote, and join the discussion; tap + in the header to submit a new one. Pull down to refresh.

For ASRR administrators

Move a finished request to Awaiting approval to hand it back to the client for confirmation. Setting Done directly still works and stays available for cases where waiting is not useful: a request the client has already confirmed elsewhere, or one nobody is going to come back to. The board then shows the request as closed by ASRR without the submitter approving, so the difference between "the client signed this off" and "we called it done" stays visible.

Super admins see an extra triage section on each request:

• Status: move the request through the roadmap stages; declining requires a reason that is shown to the submitter
• Link task: connect the request to an internal task (by task number) or create a new task in a project directly from the request; the request number is stored as the task's client reference
• Delete: remove spam or duplicates (votes and comments are removed with it)