Triage requests

Managing requests in UserJot is built around a simple workflow. New posts start in triage, then move through review, planning, delivery, and completion. The fastest way to manage that flow is the action bar on the request page, which shows the next decision you are most likely to make.

Triage new requests. New requests start in Pending. This is where you decide whether a post should move forward, be merged into an existing request, or be closed. The action bar gives you those decisions directly: accept it, merge it, or close it. If you are working through the queue, accepting or closing a request takes you straight to the next pending item.
Review what is worth doing. Accepted requests move to Reviewing. This is the filtering stage. Your team is deciding whether the request is real, useful, and important enough to plan. From here, the usual next step is to close it or mark it Planned.
Plan work that you intend to deliver. Requests in Planned are ideas you expect to work on, but have not started building yet. This is where your roadmap starts to take shape. When a request is marked Planned, it appears on the roadmap automatically if it is approved and public. From here, you can move it back to Reviewing if it is not ready, or start work when the team is ready to build.
Move active work into progress. When work starts, move the request to In Progress. This tells users and teammates that the request is being worked on now. Approved public requests also appear in the roadmap's in progress state. If work pauses, you can move it back to Planned. When it ships, mark it Completed.
Close the loop after shipping. Completed requests are done, but the workflow does not really end until users hear about it. From Completed, the action bar prompts you to draft a changelog entry so you can publish the update and close the loop publicly.
Use closed for requests you are not taking forward. A request should be marked Closed when you are not planning to work on it, when it is out of scope, or when it has been superseded. Closed requests can still be reopened later, and reopening sends them back to Reviewing.

UserJot also highlights requests that need attention even when their status has not changed. Planned or in-progress work becomes stale if it sits too long without movement, and the action bar then asks you to move it back to Reviewing or keep it where it is. A review item with very low engagement shows up as a low-traction reminder, and the action bar asks you to keep it open or close it.

If you need to make a direct change, click the status pill on the request, the first pill under the post, and pick the exact status you want. That is useful when you already know where a request should go. For day-to-day work, though, the action bar is the clearest way to keep requests moving through the intended workflow.

Workflow, review, and visibility

A request's status describes what your team plans to do with it. Moderation controls whether its content has been approved, and the Public / Private setting controls who can see it.

Accepting a request or moving it to another status does not approve content that is waiting for moderation. Closing a request does not reject or delete its content either. Use the Needs review panel to resolve the review.

Private requests and requests awaiting approval stay off the public board and roadmap, even when they are planned or in progress.

See moderate content for review actions, or make a request private to change who can see a request.

Understand the Trending badge

A request in Reviewing may show a Trending badge in the dashboard when it has received recent votes. Use it to spot requests worth another look as you work through the queue.

The badge is a dashboard cue. The public board's Trending sort determines the order of the requests shown there, so a badge does not guarantee a particular position on the board.

See how Trending works for the difference between Top, Trending, and Newest.