| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
The base layer does this transformation,
so I am not sure what this was for.
|
| | | |
| | |
| | |
| | |
| | | |
This is only used for audit purposes on FixMyStreet and not required in
Confirm.
|
| | | |
| | |
| | |
| | |
| | | |
Use a generic report description for fetched reports rather than the one
fetched over open311
|
| | | |
| | |
| | |
| | | |
Make it a bit more obvious that something has been selected.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
One off script that adds an question to each Triage category to ask if
the problem is urgent or not. Sets urgent answer to block form
submission.
|
| | | |
| | |
| | |
| | |
| | | |
Different report sent confirmation text is used for reports when they
are submitted to Triage and when they are submitted to Confirm
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Only display non triage categories on this because getting the category
expansion to work if we use the triage categories isn't in place and may
not be. This is because when we get the list of reports using
/around/ajax there's no way to know which body it is for so we don't
know how to expand a triage category to the list of 'child' categories.
So, just display the non triage ones for now.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
add a check into the Alerts script to skip comments that have
`triage_report` set in extra. Otherwise we send these our in new_updates
alerts.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If it's a standard user only display the Triage category list but if one
of these is selected then look up all the categories in that group and
use those to select the reports to display.
It it's a staff user then ignore the Triage categories.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add in some cobrand handlers to make sure
a) the appropriate categories are show to staff/non staff users on the
around and reports pages
b) that those categories are correctly expanded to the child
categories when using the category filter to search reports
This is because non staff users should only be shown Isle of Wight
categories with a send_method of 'Triage', however once those reports
are triaged the post triage categories need to be included in any
filtering
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On reports with a state of `for_triage` override the `_inspect.html`
template to display one which allows only allows the user to change the
category from one with a 'Triage' send_method to a non Triage
send_method.
When saved this records a comment with the original category and the
category it was triaged to. This is hidden from the site as it's only
used for audit purposes and sending over Open311.
This assumes that the triage categories have the same names as the
groups of the confirm categories. It uses this to select the first
confirm category in the group corresponding to the triage category.
This also makes the sidebar geolocation onclick handler check for the
presence of the button, as the triage inspect form does not have it.
|
| | | |
| | |
| | |
| | | |
sets the state of the report to `for_triage` upon sending
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This uses the Triage categories as the category names and uses the
associated groups to make sure the assets are displayed to staff users.
There is a default streets layer as a fallback for site_codes.
Some of the categories include both line and point assets so the line
assets have `display_zoom_message` in order that both show the details
of the currently selected asset.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
we want the road layers to be able to show the zoom/pick a thing/you
have picked a thing message so add a `display_zoom_message` config
option to override the `non_interative` option. We don't want to remove
the `non_interative` option as otherwise item selection hides the pin.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
check for a `fixmystreet.stopper_after` property and if present insert
the stopper element after the category extra to allow for layout
preferences.
|
| | | |
| | |
| | |
| | |
| | | |
for assets layers where we have both line and point assets it's not
helpful to have the snap threshold be very large.
|
| | | |
| | |
| | |
| | |
| | | |
These need a script to add asset_id/site_code to the category so this is
set by the front end
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Change the way we set the BBOX strategy for the map layer as otherwise
when we check for bbox_strategy in display_around this is set but has
not been associated with a layer so .activate fails.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is only used to determine if we should block sending the form
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Fixes mysociety/fixmystreet-commercial#1522
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Also tests for confirm report, report sent and alert emails.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
