| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
| |
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.)
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
Used internally to provide more details about when a priority is applicable.
|
|
|
|
|
| |
- Superusers couldn't view response priorities due to invalid $c->forward call
- Navigation to other areas of admin was broken on response priority admin pages
|
|
This moves the response priority values from a cobrand-specific method to a full
DB model, and includes management screens in the admin for administering them.
For mysociety/fixmystreetforcouncils#66
|