Where to post feedback
Ideas, requests and rough edges go on the Feedback Requests board. What belongs, what does not, and a template that works.
Ideas, requests and rough edges go on the Feedback Requests board. It is the counterpart to Where to report a bug — that board is for things that are broken, this one is for everything else.
Write in English, French, or franglais — whichever is easier. Nobody is grading the language.
What belongs here
- A feature that does not exist yet
- Something that works, but takes too many clicks
- Confusing labels, awkward ordering, a layout that breaks on mobile
- "I wish it also did X"
- A missing or wrong documentation page
Friction counts. "It works but it is painful" is real feedback — it is not a bug, and it is not nothing.
What does not belong here
Instead of posting here… | Go to |
|---|---|
Something is broken or erroring | The Bug Reports board |
A missing or wrong movie, show, music, photo | |
"How do I…?" | |
Something urgent or private | |
A feature request for Quackback itself |
Before you post
- Search the board. If it already exists, vote on it and add a comment with your own use case. That is worth more than a duplicate, which splits the votes.
- Check the wiki. Sometimes it already exists and is just hard to find — which is itself worth posting about.
- One idea per post. A post bundling four requests cannot be given one status or closed by one release.
Lead with the problem
This is the single biggest thing that decides whether a request goes anywhere.
- Weak: "Add a dark mode toggle"
- Strong: "I use Think at night and the bright interface strains my eyes"
The second attracts votes from everyone who shares the problem — including people who imagined a different solution — and it leaves room for a better answer than the one you thought of.
A template that works
## Who it is for
As a [type of user], when I [situation],
I want [outcome] so that [benefit].
## What is needed
Feature X in ThinkY. Or: a new application to do Z.
## Done when
- [ ] The button appears only for signed-in users
- [ ] It is labelled "Logout"
- [ ] Pressing it opens a confirmation with OK and Cancel
## Anything else
Screenshots, examples from other tools, workarounds you use today.The Done when list matters most. Each line should be verifiable by someone else without asking what you meant:
- Works: "Pressing it opens a confirmation with OK and Cancel"
- Does not work: "Logout button" — built how, looking like what, behaving how?
Etiquette
- Do not comment "+1". Vote instead — that is what votes are for, and empty comments bury useful ones.
- Do add your use case, even on a request that already exists.
- Do not ask for an ETA or a roadmap slot. Think runs on open-source projects maintained in people's own time.
What happens next
Your post lands in Open and you are subscribed automatically. See What happens to your feedback request for the full path from posting to shipping.
Was this helpful?
Your feedback shapes what we write next.