Issues

Issues is how you tell us something is wrong, ask for something new, or ask a question. It replaced Feedback: everything filed from here on lives here.

What this section is for

One queue per part of the app, one conversation per report. You file an issue, it lands with whoever looks after that part of the app, and the two of you talk in a single thread on the report until it is closed.

Key pages at a glance

Your issues (/Issues) — the list, with the selected issue's detail beside it
File an issue (/Issues/New) — the full form
The help button — on any page: Create issue opens the same form in a pop-up without losing your place

As a Volunteer

File an issue

Use the help button on any page and choose Create issue, or go to /Issues/New. Filing from the help button records the page you were on, which usually saves a round of "where were you when this happened?".

You fill in:

Title — up to 200 characters
Type — Bug, Feature, or Question
Area — which part of the app, if you know. Leave it blank if you don't; it goes to the admins, who will route it
Description — up to 5,000 characters
Attachment — optional screenshot: JPEG, PNG, or WebP, up to 10 MB

Follow it

/Issues shows every issue you reported, whatever its state, with a search box over titles and descriptions and filters for status and type. Open one and you get the whole history: your report, every reply, and every change a handler made to it.

Write in the same thread to add anything — the composer supports Markdown formatting. You get an email whenever a handler replies — in your language, with their message in it.

If it gets closed and you're still stuck

Comment on it. A closed issue reopens the moment its reporter says something else on it, and goes back into the handler's queue.

How long it's kept

Six months after an issue is finally closed, it and its attachment are deleted for good.

What you can't see

Other people's issues. You see exactly the ones you reported — no more, in any area — unless you hold a role that owns a queue.

Automation

/api/backdoor/issues is key-authenticated (X-Api-Key), using the personal key an admin allocated to you at /Backdoor. It lists and reads issues, files one, comments, and changes status, assignee, area, or the linked GitHub issue. Anything it writes is attributed to the human whose key was used.

A comment posted through the API counts the same as one in the browser: if the key belongs to the issue's own reporter, it's a reporter reply and reopens a closed issue.

Feedback — the retired predecessor; its archive is still there for admins
The in-app AI helper — try it first for a question; it can file an issue for you
Admin — roles are assigned on the admin role pages; API keys are allocated at /Backdoor