| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| |
|
|
|
|
| |
Add a single_body_only form value to reports that contains the name of
the only body to send the problem to. If the name doesn't match any of
the valid bodies for the report then send to all.
|
| |
|
|
|
| |
test to check creating a new report for a category for which there are
multiple bodies
|
| | |
|
| |
|
|
|
|
|
| |
When pulling reports in over Open311 it's sometimes useful to be able to
accept reports with Easting/Northing rather than latitude/longitude.
This adds an option to GetServiceRequests to convert them as they
come in.
|
| |
|
|
|
|
|
| |
Comments added offline by an inspector set the time in JavaScript using
a UTC epoch. We need to add the FMS timezone to this so it's in the
timezone the database expects for timestamps otherwise it's incorrect
when we fetch it back out
|
| |
|
|
|
|
| |
Hides the empty “Help <council> resolve your problem quicker” section of
the new report form if report metas for the selected category are all
hidden fields.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
If the Open311 endpoint provides the external_status_code field
in servicerequestupdates.xml output, it’s stored in each comment’s
extra field as well as the problem’s extra field. This will make it
possible to trigger response templates based on this value.
|
| |
|
|
|
| |
We do need to store them, so that the sending knows which fields are being
requested, but we do not want them output to the client at all.
|
| | |
|
| |
|
|
|
|
| |
If the map was not clicked and we don't have a postcode we should still
send the easting and northing extra attributes if send_notpinpointed is
set.
|
| |
|
|
|
| |
Store if the report/update was created by someone using the contributed-as
dropdown, and use that information to perhaps not send report-sent emails.
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
This fixes #2023 by removing the comma.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
Add a per body configuration option to allow Open311 updates to contain
only a status change, rather than emitting a warning when this happens.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This is part of the integration with our open311-adapter. The automated
property indicates that it's an expected value but either it's going to
be set by the server, or appear as a hidden field.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Per cobrand configurable option to send multiple photos over open311
instead of just a single one. Does this by sending multiple media_url
parameters in the POST body.
The default remains to send the first photo associated with a report.
|
| | | |
| | |
| | |
| | |
| | | |
Web and email template changes, CSS plus cobrand file with open311
config
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This enables the display of existing reports from the back end on FMS
if the body is configured to do this.
Reports will not be created if they are missing an id, a lat or a long,
if the lat/long is outside the area covered by the body, if there is
already a report with a matching id, or if we can't parse out the
request time.
|
| | | | |
|
| |/ / |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Zurich code was written a long time ago, and used overriding so that
e.g. the hard-coded 'investigating' state referred to Wunsch (wish). Now
that states are stored in the database, we can create ones specially for
Zurich and use them instead. Hooray!
|
| | | | |
|
| | |/ |
|
| |/
|
|
| |
Add an update with each report closure.
|
| |\ |
|
| | |
| |
| |
| |
| | |
The code for moving a report to the intermediary state was running
even if the report was in a closed state and had not been changed.
|
| | |
| |
| |
| |
| | |
If you rotated a photo, updates and the category list weren't loaded. If you
changed a report's state, the map pin colour was derived from the old state.
|
| |/ |
|
| | |
|
| |
|
|
|
| |
The addition of e.g. questionnaire_id to an update's
extra field means this check has to be more nuanced.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This means the questionnaire is considered 'answered' as soon as
a (HTML) link is clicked, which I think is okay. Then filling in
the questionnaire form will update the same questionnaire.
|
| | | |
|
| | |
| |
| |
| |
| | |
This means we don't show separate 'Still open' messages
when an update was also left at the same time.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| | |
This allows more fine grained control over the geocoder search, e.g. to
specify the administrative area or town. See the geocoder api docs:
https://developers.google.com/maps/documentation/geocoding/intro#ComponentFiltering
|
| |/
|
|
|
|
|
|
| |
Make sure that the prettify_dt tests use the same timezone as FMS
otherwise the test can fail if now in the local timezone is actually
yesterday/tomorrow in the FMS timezone.
Fixes #1984
|
| | |
|
| |
|
|
|
|
|
| |
Previously this would force phone_verified to false for all user edits,
as well as forcing email_verified to true - which would be the wrong thing
to do if the user had been created/verified via the ‘report as another user’
flow.
|
