Skip to content

HomeDocsUsing ReqioStatus pipeline

Using Reqio

Status pipeline

How requests move through Needs action, In progress, and Completed, and what happens to subscribers at each step.

Every request in your backlog has one of three statuses. Moving a request through the pipeline automatically notifies the people watching it, so you do not need to chase anyone down.

The three statuses

Needs action

The default for every new submission. You have seen it, but nothing has been decided yet.

From Needs action you can:

  • Move it to In progress when you decide to work on it.
  • Move it to Completed to close it directly, for example if it is a duplicate, already shipped, or out of scope.

In progress

Work is underway. When you move a request into In progress, subscribers (people who upvoted or submitted it) automatically receive a notification that the team is working on it. This is the moment most users want to hear from you.

Completed

The request is resolved. Subscribers receive a completion notification. You choose how it was completed:

  • Shipped: it is live now.
  • Coming in the next update: it is finished but not yet released.

The completion type changes the notification copy your users see.

Changing a status

  1. Open the request and pick a status

    Use the status selector to pick the new status.

  2. Review the notification

    Before the notification is sent, you can edit the message text and confirm.

  3. Confirm, or undo

    A short countdown gives you a moment to undo if you change your mind. The notification is only sent once the countdown finishes.

Reopening a completed request

If a user replies to a completed thread, the request automatically reopens to Needs action. The same happens if you move it back manually. The completion type is cleared.

Category rules

The available status transitions depend on the request category.

Request (Feature)Full pipeline
Needs action, In progress, Completed.
ErrorFull pipeline
Needs action, In progress, Completed.
FeedbackSkips In progress
Needs action, Completed.
QuestionSkips In progress
Needs action, Completed.

Feedback and Question submissions skip In progress. A feedback item is either open or answered. Moving it directly to Completed when you reply is the intended flow.

Notifications

Two notification points

Reqio sends subscribers a notification at two points: when a Request or Error moves to In progress, and when any request moves to Completed.

Notifications appear in the widget for the user and, if you have email configured on the project, as an email to identified users. Users who have an email address stored in Reqio (either because they provided it directly or because your server sent it in an identity token) receive both the in-widget notification and the email.

To set up email notifications, configure your project's email settings in Settings → Email.