How the Feedback Portal works

What this portal is for, what belongs here, and where everything else goes.

T
Written By thinkheadLast updated about 6 hours ago

ThinkFeedback is where you tell us what is broken, what is missing, and what is awkward — and where you can watch what happens to it afterwards.

Three things you can do here:

  • Browse what other people have already reported or asked for
  • Vote on the things that matter to you
  • Post something that is not already here

Write in English, French, or franglais. Nobody is grading the language.

What belongs where

You want to…

Go to

Report something broken in a Think service

The Bug Reports board here

Ask for a feature, or flag an awkward workflow

The Feedback Requests board here

Report a missing or broken movie, show, music, audiobook or photo

ThinkRequest

Ask "how do I…?"

The wiki first, then Discord

Escalate something urgent or private

ThinkComplaints

Report a bug in Quackback itself

Quackback on GitHub

Two boards, one pipeline

There are only two boards — Bug Reports and Feedback Requests. Everything posted to either is a post, and every post moves through the same six statuses.

Pick the wrong one and it does not matter: an administrator can move it, and it keeps its votes, comments and history. Reposting is what causes damage, because it splits the votes across duplicates.

What happens to a post

Status

On the roadmap?

Meaning

Open

No

Posted, awaiting triage

Needs Info

No

Waiting on you — it cannot move until a question is answered

Under Review

No

Being evaluated for effort, risk and priority

Planned

Yes

Accepted and queued — no date attached

In Progress

Yes

Actively being worked on

Upstream

Yes

Accepted, but the fix belongs to the upstream project

Deferred

No

Accepted in principle, but not in this phase

Complete

Yes

Released

Closed

No

Closed without action, with a reason

Duplicate

No

Merged into an existing post, which keeps the votes

Out of Scope

No

Not something Think will take on

Under Review

Being evaluated for effort and priority

No

Planned

Accepted, queued — no date attached

Yes

In Progress

Actively being worked on

Yes

Complete

Released

Yes

Closed

Declined, duplicate, or no longer relevant

No

Reaching the Roadmap is the acceptance announcement — nothing is announced separately. When it ships it appears in the Changelog with a version number, and anyone subscribed to the post is told.

Ground rules

  • Search before posting. Vote on the existing post instead of creating a duplicate.
  • Do not comment "+1". That is what votes are for.
  • One issue per post. A post covering four problems cannot be given one status or closed by one release.
  • Do not ask for an ETA. Think runs on open-source projects maintained in people's own time.

This portal is not wired to anything else

Posts here do not sync to any external issue tracker. If work needs tracking elsewhere, an administrator links it by hand, and nothing flows back automatically. Keep the discussion on the post.

Was this helpful?

Your feedback shapes what we write next.