| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
When the category or state changes, the list of available templates
updates (previously it was frozen at what the category was on page
load, and didn't care about the state).
|
|
|
|
| |
Also include areas in auto-generated problems.
|
|
|
|
|
| |
This now lets the response priority and defect type handling share the
same code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Historically in UK cobrands, bodies have had IDs the same as the MapIt
area ID they cover. This can be confusing (if you are setting up a dev
environment, say) and should not be necessary. This commit removes the
requirement entirely, by switching any ID checks to either the name of
the body, or the actual area it covers.
One note: the body name in the test has to match so that we do not get
two bodies both covering 2237 created. This will not be necessary when
the tests are compartmentalized in the next commit.
|
|
|
|
|
|
| |
Given a MapIt area ID, the script will create a body and categories,
users with different levels of permissions, and some random problems
and updates. It can optionally empty out the database first.
|
|
|
|
| |
Add hook so that cobrands can change pin hover title.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Problems can have an associated defect type, that can be assigned during
an inspection. Include an admin interface for managing these types, that
can also be assigned on a per-category basis, currently available to the
Oxfordshire cobrand.
(Also include 'TM' in traffic management Exor RDI output.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid doing cobrand-specific logic within SendReport::Open311.
The hooks defined are:
open311_config: set extra fields
open311_pre_send: set endpoints and munge data
These are tested in the new t/app/sendreport/open311.t, which does
not send any actual reports, but just checks that all the data is
munged into the expected format. (tests under t/open311* should
already test the actual sending)
Remove unused Open311 special cases.
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#98
|
|
|
|
|
|
|
|
|
|
| |
The RDI file format encapsulates information about inspections that have taken
place, and can be uploaded into Exor to create defects in bulk.
This commit adds a page to the Oxfordshire cobrand's admin allowing RDI files
to be generated and downloaded from FMS.
For mysociety/fixmystreetforcouncils#127
|
| |
|
| |
|
|
|
|
|
|
| |
This method creates a token that logs the reporting user in, optionally
with some parameters which are stored with the token for use when redirecting
after login.
|
| |
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#159
|
| |
|
|
|
|
|
|
|
|
|
| |
Adding an official badge to Greenwich updates so as to avoid exchanges in which
public contributions are mistaken for official ones.
As per the Bromley version e.g. https://fix.bromley.gov.uk/report/973784 - this
helps to avoid situations where public contributions are mistaken for official
ones.
|
|\ |
|
| |
| |
| |
| | |
Bromley had this already in its update state change messages.
|
|/
|
|
| |
This joins easting, northing and an external ID field.
|
| |
|
|\
| |
| |
| | |
'origin/issues/forcouncils/136-show-user-details-for-council-report'
|
| | |
|
|\ \
| | |
| | |
| | | |
'origin/issues/forcouncils/142-allow-anonymous-council-updates'
|
| | | |
|
| |/ |
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
This includes adding/removing reports from a user's shortlist, and
manual reordering of a shortlist with up/down buttons.
The backend code can cope with an item moving to any point in the list.
|
|/ |
|
| |
|
|
|
|
| |
This should help if a template uses has_permission_to a lot.
|
|\ |
|
| |
| |
| |
| |
| | |
Different categories may have a different list of priorities, so store
them all and update as the category changes.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Use Problem->pin_data for single report page
- Promote markers_highlight to fixmystreet.maps API
We want to highlight map pins on the duplicate report selection UI, so let's use
what's already there instead of writing something new.
- Make sure duplicate report pins aren’t draggable
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Prevents potential odd-element hash in e.g. response_priorities.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Includes newest, oldest, least/most recently updated, and most comments.
The default remains the same, which is last updated on /reports, and
newest on /my and /around (the latter plus not-in-view
sorted-by-distance ones).
|
|\ \
| |/
|/| |
|
| | |
|
|/
|
|
|
| |
This pre-filters the 'all reports' link in the main nav and the /around page
reached via the front page postcode form
|
|\ |
|