What the statuses mean

All eleven statuses explained: which need something from you, which appear on the roadmap, and what Deferred, Upstream and Out of Scope really mean.

Every post — a bug or a piece of feedback — carries exactly one status. It is the honest answer to "what is happening to my post?", and it is the only thing that decides whether the post appears on the Roadmap.

There is one set of statuses. Bugs and feedback do not have separate workflows.

The short version

Status	Roadmap	In one line
Open	No	Received, not yet looked at
Needs Info	No	We are waiting on you
Under Review	No	Being weighed up
Planned	Yes	Accepted, in the queue
In Progress	Yes	Being worked on now
Upstream	Yes	Accepted, waiting on someone else's fix
Deferred	No	Good idea, wrong time
Complete	Yes	Shipped
Closed	No	Not going ahead
Duplicate	No	Already posted by someone else
Out of Scope	No	Not something we will take on

While it is being considered

Open

The default for everything you post. It has been received and is waiting for triage. Votes gather here, so this is where saying "me too" — by voting — has the most effect.

Needs Info

This one needs you. Something is missing and the post cannot move until it is answered: which browser, exact steps, whether you were signed in, what time it happened.

If your post is sitting here, check the comments. It is the single most common reason a post goes quiet, and it clears the moment you reply.

Under Review

Being weighed up — effort, risk, how many people it affects, and whether it fits what the platform is doing right now. Nothing is required from you.

Once accepted

Planned

Accepted and queued. Planned does not mean scheduled — there is no date, and asking for one will not produce one. It appears on the roadmap the moment it reaches this status, which is how acceptance gets announced.

Voting still helps here: Planned items are ranked against each other.

In Progress

Someone is actively working on it. It stays on the roadmap throughout.

Upstream

We agree with you, and we cannot fix it alone.

Most Think services run open-source applications we deploy rather than write. When the change belongs inside one of those applications, we report it to that project and your post tracks it from here. It stays on the roadmap because it is accepted work — it is just not work we control the timing of.

Sometimes the outcome is a workaround on our side, a configuration change, or eventually replacing the application. See Where to report a bug for how we tell "ours" from "theirs".

Deferred

This is not a rejection. The idea is accepted in principle, but the platform is in a phase focused elsewhere, so it is not being picked up now. It will be revisited when the phase changes.

If your post is Deferred, the useful thing to do is keep collecting votes on it — that is what argues for it in the next phase. See How versioning works for what phases are.

Finished

Complete

Done and released. It appears in the Changelog with a version number, and everyone subscribed to the post is notified.

If something is marked Complete but is still broken for you, say so on the same post rather than opening a new one — that keeps the history together.

Not going ahead

All three of these keep the post visible, with its votes and comments intact. Nothing is deleted, so the reasoning stays readable.

Closed

Closed without action, always with a reason in the comments. Typically: it turned out not to be a problem, it was expected behaviour, or it stopped being relevant.

Duplicate

Someone already posted it. The post is merged into the original so the votes end up in one place instead of split across two. Follow the original — it is linked from the comments.

This is why searching before posting matters: duplicates dilute the exact signal used to prioritise work.

Out of Scope

Not something Think will take on. Usually it belongs somewhere else entirely:

A missing or broken movie, show, or music track — that is ThinkRequest
Something urgent or private — that is ThinkComplaints
A request for a third-party service Think does not run

It always comes with a reason, and usually a pointer to the right place.

What decides the status

Triage weighs reach, severity, effort, risk, and whether something unblocks other work. Bugs and feedback are weighed differently — a reproducible bug that breaks something important skips the vote queue entirely, while votes matter far more for feedback.

The full detail is in What happens when you open a bug and What happens to your feedback request.

Every change is recorded

Each post carries a timeline showing every status change and who made it. Nothing moves invisibly, and you are subscribed automatically to anything you post or comment on — so you do not have to watch.