Report a problem
When something in the Explorer looks wrong — the results on a page, or the page itself — you can tell us from that page without losing your place. You write what looked wrong and how much it is holding you up; the Explorer saves the page and what it was showing, so the rest comes with it. Later you can see what happened to anything you reported.
Reporting a problem
Every page has one way in: the bug icon in the header, Report a problem in your account menu, or the b key. A short dialog opens for the page you are on. A background run that could not be completed also has a Report button on its notification, which sends the run with your report.
The dialog shows what goes with your report under Sent with it: the page's address always, and what the page names, such as the property, the council and quarter of a sources page, or the run. You cannot edit it; it is what you were looking at.
What kind of problem
Pick the kind that fits best: Wrong data, Odd answer, Too slow, Screen fault, or Something else. It is your first guess, and we may file it under another kind once we look. Then write what you saw, and what you expected.
How much it holds you up
Say how much it is holding you up: a nuisance, blocking part of my work, or stopping me. Nothing is picked for you, and Send report waits until you choose. A short note confirms the report is sent, and you stay where you were.
Tracking your reports
Your reports are listed under Notifications › Bug reports, newest first: what you wrote, where it has got to, and the date you sent it. Click one to open it: our reply once there is one, the kind you picked, and what was sent with it. Check back here for replies; we may also email you.
The bin beside a report dismisses it: it leaves your list, and we keep it. A report still In the queue can also be withdrawn from inside it, if you sent it by mistake; once we have started on it, you can only dismiss it. Both ask for a second click to confirm.
What the statuses mean
- In the queue — received, and waiting for the next triage pass.
- Looking into it — being looked at now; we will follow up as we learn more.
- Referred upstream — passed to the team that maintains the source data; we will tell you when the source rebuilds.
- Fix scheduled — reproduced on our side and a fix is scheduled; we will tell you when it ships.
- Fixed — now fixed; the reply says what changed, so you do not have to re-run anything to find out.
- Closed — outside what we can address; the reply says why.