| 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.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Removes the FixaMinGata Geocode module
- Surround bounds coordinates with quotes
- Return a different bounding box for Öckerö and other places
- Specifies specific GPS coordinates for certain OpenStreetMap relations
- Removes a comment
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
For controlling if reports pulled in via Open311 should have the
position converted from Easting/Northing to lat/long.
|
|/
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Displays the category’s email address (service code, for Open311) as
a tooltip. This makes it easier to identify the right category when
editing response templates, for example.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Upgrade Test::PostgreSQL, which fixes a bug delaying the end
of test running, and introduces a nicer setup mechanism.
|
|/ |
|
|
|
|
|
| |
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.
|
| | |
|
|/
|
|
| |
Then it can skip working out some things as they are not needed.
|
|\ |
|
| |
| |
| |
| | |
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.
|
| | | |
|
|/ / |
|
|\ \ |
|
| | | |
|
|/ /
| |
| |
| |
| | |
This allows users (e.g. customer service staff) to search for a user's
reports in the admin without being able to edit them.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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!
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This variable existed to keep a copy of the categories before it was
overwritten by report_edit_location (if a bad location was provided)
calling the variable setup functions again. But really, the function
shouldn't be overwriting the stash, it's only testing the lookup and
so should restore the stash at its end.
|
| | |
| | |
| | |
| | | |
Remove old unused setup-contacts code, superceded by fixtures.
|
| | |
| | |
| | |
| | | |
Adapt look of default dashboard filtering.
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
|