| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
At the moment if you fetch a report in a staff category it will still be
created but will be in the Other category. Given that some staff
categories are marked as private this can allow reports that should be
private to be put in a public category.
|
|
|
|
|
|
| |
Given the user, we can infer the name if not provided, and the extra
data if a staff user. We can also provide defaults for various other
fields. Always have superuser take precedence over from_body.
|
|
|
|
| |
This simplifies the code wherever used.
|
|
|
|
|
| |
Make GetUpdates and GetServiceRequestUpdates share a common base;
spot all visible states.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This includes details of any failing updates in the summary script.
|
| |
|
|
|
|
|
|
|
| |
Adds a new tickbox to the contact editing form that protects the category
and group names from being changed by Open311.
For mysociety/fixmystreet-commercial#1776
|
|
|
|
|
|
|
|
| |
Order the response templates query by external status code so if you
have an update with an external status code the response template
matching that is always used. Previously with the database left to
determine the order it could pick a response template with a matching
state rather than a matching external status.
|
| |
|
|
|
|
| |
Allow a configurable number of bodies to fetch updates simultaneously.
|
|
|
|
|
| |
Make them take start/end hour arguments, cope if only one given,
optional body, and combine them together in one `fetch` script.
|
|
|
|
| |
contacts
|
|
|
|
| |
column
|
|
|
|
|
|
|
| |
To avoid issues with autogenerated updates in the bodies back-end
happening quicker that the back-end returns the external_id to us ignore
the check for comment being earlier than the last update if it's the
first comment.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
It arises that <group></group> now passes to the code as a one-element
list containing undef, which compared differently to what was stored -
the code assumed lists would contain things. A new changelog entry was
created each time. Hopefully resolve this once and for all by treating
groups more formally and making sure we always have lists to compare.
|
|
|
|
|
| |
This is only used for audit purposes on FixMyStreet and not required in
Confirm.
|
| |
|
|
|
|
|
| |
If an extra field on a category has a protected flag then do not
overwrite or remove it when populating categories.
|
|
|
|
|
|
| |
If an update with a blank external_status_code is fetched then unset it
otherwise we will always a detect a change in the external_status_code
which might mean phantom updates.
|
| |
|
|
|
|
| |
Lots of false positives from other bodies too.
|
|
|
|
|
| |
By specifying a placeholder in an email template, it can be replaced
by the description returned from the Open311 server.
|
|
|
|
|
|
|
| |
Only parses as multiple groups if cobrand is configured to handle them
to stop issues with existing groups with commas in them.
Groups are parsed as CSV so as to allow commas in group names.
|
|
|
|
|
| |
Rather than have a method in the Cobrand module use the COBRAND_FEATURES
section of the config file.
|
| |
|
|
|
|
|
|
| |
This change ensures that a report fetched via Open311 for a non_public category
will always be marked as non_public even if its Open311 XML doesn’t explicitly
include the non_public tag.
|
|
|
|
|
|
|
|
|
| |
This allows the Open311 endpoint to include ‘private’ in the ‘keywords’ field
of a service definition in order for it to be marked as non_public on FMS.
NB existing categories may be updated to become non_public, but non_public
categories will never have their non_public flag unset by PopulateServiceList.
This is so any existing Open311 categories on FMS don’t suddenly become public.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Times in the database should be stored in the application server's local
timezone, by e.g. using `current_timestamp`, or by setting that timezone
explicitly before storage (the database columns are all without timezone
so any timezone info is silently ignored). Reports & updates fetched via
Open311 and offline updates were being put into the TIME_ZONE setting if
present, meaning they were stored incorrectly for future usage.
|
|
|
|
|
| |
If an update has a fixmystreet id in it check that it looks like an
integer and if not issue a warning and skip the update.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
The test has to now create a new comment object each time as
`get_cobrand_logged` is cached on the object.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If an update has a fixmystreet_id field then use the contents of that in
preference to the external_id field to match an update to a problem.
This handles the case where a report in a third party system passes
through different types (eg inspection and defect), resulting in the
external id changing. In this case it is sometimes possible to include
the fixmystreet id in each type and hence use that to match things up at
the fixmystreet side.
|
|/
|
|
|
| |
Otherwise running on a site where one body ID is a substring
of another, comments can get processed for the wrong body.
|
| |
|
| |
|
|
|
|
|
| |
When fetching reports run them through the cobrands
filter_report_description method if it exists.
|
|
|
|
|
|
|
|
|
| |
If there is
<non_public>1</non_public>
tag in an incoming service request then set the created report to
non_public.
|
|
|
|
|
| |
If we fail to match an update to a problem on the staging server then
print a warning so we can diagnose issues.
|