Where to report a bug

Bugs in Think services belong on the Bug Reports board here. You do not need a GitHub account, and you do not need to work out which underlying application is at fault — describe what you saw, and we will work that out.

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

First: is it actually a media request?

For a problem with a movie, TV show, music, audiobook or photo in Plex — missing, wrong, or broken content — use ThinkRequest instead. Those go through a different queue entirely and will be closed here.

Before you report

• Search the board first. If it is already reported, vote on it rather than posting again.
• Check the wiki — the FAQ for that service may already explain it.
• Try a private window. It rules out a browser extension, a surprisingly common cause.
• Ask if you are unsure. There is no penalty for asking first.

Board etiquette

• Do not comment "+1" or "I am interested in this". Vote instead — that is what votes are for, and empty comments bury the useful ones.
• Do comment if you have something new: your circumstances, a different reproduction path, a screenshot.
• Do not ask for an ETA or a roadmap slot. Think runs on open-source projects maintained by people in their own time.
• Do use the template below. It exists so you do not have to guess what is useful.

What to include

• Current behaviour — what actually happens
• Expected behaviour — what you thought would happen
• Steps to reproduce — numbered, as thorough as you can manage
• Your environment — operating system, browser, which Think service, and roughly when

A template that works

Posts support markdown. The Markdown Guide cheat sheet covers the syntax if you need it.

## What happened

A short description of the problem.

## Steps to reproduce

1. Go to ...
2. Click ...
3. See the error

## What I expected

What should have happened instead.

## What I got

What actually happened. Paste the exact error text if there was one.

## Environment

- Service: ThinkCloud / ThinkLinks / ...
- URL: https://...
- Browser + OS: Firefox 153 on Windows 11
- When: 2026-08-15 12:12
- Signed in: yes / no

## Anything else

Screenshots, workarounds you found, whether it happens every time.

"Is this even our bug?" — you do not have to decide

This is the most common reason people hesitate, so to be clear: report it here either way. Working out whether a problem belongs to Think or to the application underneath is our job, not yours.

It helps to understand the difference, though, because it shapes what happens next.

Probably ours — how Think runs the application

These are almost always something we configured, and we can usually fix them ourselves:

• Signing in — SSO failures, being asked to log in repeatedly, permission errors
• Reaching the service — the URL not loading, certificate warnings, timeouts
• Missing or wrong data after a move — content that vanished following a migration
• Two services not talking to each other — one Think service failing to reach another
• Storage and uploads — files failing to save or images not appearing
• A service that is simply down

Probably upstream — how the application itself behaves

These live in the open-source application we deploy, not in our configuration:

• A feature inside the app behaving incorrectly
• Layout or rendering problems within the app's own interface
• An error message clearly produced by the application
• Something that would break identically on anyone else's install

We cannot patch someone else's application directly. What we do instead: reproduce it, report it upstream, and link that report to your post. Your post stays open here and tracks the upstream fix, so you still get told when it lands.

Sometimes the answer is a workaround, a configuration change on our side, or — if the project is abandoned — replacing the application entirely. That is exactly how ThinkBugs became ThinkFeedback.

One genuine exception

If the bug is in Quackback, the software running this portal, it can go straight to Quackback's GitHub issues. Posting it here works too; that just adds a step.

What happens next

Your post lands in Open and you are subscribed automatically. See What happens when you open a bug for the full triage path.

Urgent, private, or going nowhere

• ThinkComplaints — for anything needing escalation rather than votes, or that should not be public
• Discord — for a faster answer, or to check whether anyone else is seeing it before you post