Faults we already know about, what they look like, and what to do in the meantime. If you hit something that is not on this list, it is worth reporting.
Affects: Anyone adding a property through Submit a Property
What you see: The property saves and appears in the full list, but it has no region attached, so filtering by region will not show it.
What to do meanwhile: Find the property through the full list or by searching its name rather than by filtering on region. Adding properties through the spreadsheet import is not affected - that path sets the region from the postcode.
Open - fix in progress
Affects: Anyone comparing the app against the master spreadsheet
What you see: The app holds 179 properties from a 189-row sheet. Three rows have data but no name in the UUID column, and six names appear on two rows each, so the second row overwrote the first.
What to do meanwhile: The import now refuses unnamed rows and reports duplicate names with their line numbers, so the affected rows are listed every time it runs. They need distinct names in the sheet before they will import.
Open - needs a data decision, not a code change
Affects: Anyone comparing region scores against property scores
What you see: Region scores and property scores are on different scales, so the combined score blends two things that were not measured the same way.
What to do meanwhile: Compare properties against each other within a region, where the site scores dominate and are directly comparable.
Open - migration planned
The most useful report says what you did, what you expected, and what happened instead. A property name or a link to the page is usually enough for someone to reproduce it.
Issue trackerSecurity problems are not listed on this page. If you think you have found one, report it privately rather than on the public tracker.