| 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).
|
|
|
|
|
|
| |
Instead of checking if the list of bodies has changed at all, mark the
report for resending if there is a body in the new list not present in
the old.
|
|
|
|
|
| |
This now lets the response priority and defect type handling share the
same code.
|
| |
|
|
|
|
| |
This means that the tests can be run in parallel.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Add hook so that cobrands can change pin hover title.
|
| |
|
| |
|
|
|
|
|
|
| |
The Bromley update form needed to be updated to use the new <select> template.
This also fixes a situation where staff users (on all cobrands) wouldn't be able
to leave updates on problems with state 'fixed - user'.
|
|
|
|
| |
This lets it look the same as admin/inspect uses, with optgroups.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Allow find_closest to be called multiple times with only one lookup,
and to return just its data, not a compiled string.
|
|
|
|
|
|
|
|
|
| |
Update the reports with a bounding box, similar to on around pages.
This is made slightly trickier because we don't want to do anything
on page load (we already have the pins), we need to reload when the
zoom changes, and we don't want the strategy to get confused by its
first redraw, e.g. on pin hover, We also need to turn off the zoom-
to-bounds if we've got a bounding box in the URL.
|
|
|
|
|
|
| |
As the templates were using `grep`, they failed to match on a category
such as "Footpaths (right of way)". Changing the stash variables to be
hashes instead of lists makes checking for a key simpler. Fixes #1688.
|
|
|
|
|
|
|
| |
The report-sending code has allowed multiple emails for a long time, but the
admin wouldn't allow you to enter multiple emails for each contact.
Fixes mysociety/FixMyStreet-Commercial#835
|
| |
|
|\ |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
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.)
|
|
|
|
|
|
|
| |
The Open311 JSON output was wrapping each request parameter in a list.
This was presumably to prevent the XML output including the parameters
as attributes rather than children. A better way to fix this is to use
the NoAttr parameter to XMLout which forces them to be children.
|
|
|
|
| |
This works better if e.g. a user stops being associated with a body.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The interception of 404s etc is too much of an inconvenience.
|
|
|
|
|
|
|
|
|
|
|
| |
Reports in the generated Exor RDI file need to have an external_id so they can
be linked to existing enquiries (PEMs) when the RDI is imported into Exor.
There is a small window of opportunity for a report to be created, inspected and
downloaded in an RDI before it's been sent to Exor via Open311 and had an
external_id assigned. This commit closes that window by excluding reports from
the RDI that don't have an external_id.
Fixes mysociety/fixmystreetforcouncils#168
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than assigning +1 to a user's reputation every time a report is
inspected, this allows cobrands to specify which states should increment or
decrement the reputation value when a report is inspected.
The default behaviour is for reputation to never be changed, but the Oxfordshire
cobrand will increment the reputation when a report is marked as 'action
scheduled'.
For mysociety/fixmystreetforcouncils#119
|
|
|
|
|
|
| |
A report is now considered 'inspected' if its state was changed by an inspector.
Additionally, an AdminLog entry is created so the time of inspection and
inspector can be recorded.
|
| |
|
| |
|
|
|
|
|
| |
Tokens can include a 'p' field in their data to set query params for the
post-login redirect URL.
|
|
|
|
| |
If the user has a from_body and at least one category set.
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Assume that if they inspect and save a report, they want
to go back to their shortlist.
|
|/ |
|
|
|
|
|
| |
Solves a minor bug where it was difficult to create a new user and immediately
assign permissions, as the page didn't show the appropriate permissions UI.
|