| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|
|
|
| |
This has been running for a year, added in e17eb20.
|
|
|
|
| |
This works better if e.g. a user stops being associated with a body.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than assigning +1 to a user's reputation every time a report is
inspected, this allows cobrands to specify which states should increment or
decrement the reputation value when a report is inspected.
The default behaviour is for reputation to never be changed, but the Oxfordshire
cobrand will increment the reputation when a report is marked as 'action
scheduled'.
For mysociety/fixmystreetforcouncils#119
|
|
|
|
|
|
| |
A report is now considered 'inspected' if its state was changed by an inspector.
Additionally, an AdminLog entry is created so the time of inspection and
inspector can be recorded.
|
|
|
|
|
|
|
|
|
|
| |
Limits the state dropdown to those states which will be useful to OCC
inspectors, as well as removing a few from the base template on the inspect
form. Some slight template refactoring has made it easier for other cobrands to
override the list, as well as sharing the template with the admin report_edit
form to allow all states to be selected.
Fixes mysociety/fixmystreetforcouncils#129
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#159
|
| |
|
| |
|
|
|
|
| |
Bromley had this already in its update state change messages.
|
| |
|
|\
| |
| |
| | |
'origin/issues/forcouncils/136-show-user-details-for-council-report'
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | | |
'origin/issues/forcouncils/142-allow-anonymous-council-updates'
|
| |/ |
|
|/
|
|
|
|
|
| |
This includes adding/removing reports from a user's shortlist, and
manual reordering of a shortlist with up/down buttons.
The backend code can cope with an item moving to any point in the list.
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
f58ce6c4 changed the base contact template to include a link to a
fixmystreet.com specific page. Revert this back and make the change
in the correct cobrand only.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
Different categories may have a different list of priorities, so store
them all and update as the category changes.
|
| |
| |
| |
| |
| |
| | |
- Record state change when leaving update and marking as duplicate
- Change save button wording to match problem state when inspecting
- Make it clearer that updates marking a report as duplicate actually close the report
|
| |
| |
| |
| | |
This stops updates being left on duplicates.
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
Mock out the DNS lookup to fail, in case the test is being run somewhere
where the ISP hijacks NXDOMAIN results and redirects them elsewhere.
|
|
|
|
|
| |
This pre-filters the 'all reports' link in the main nav and the /around page
reached via the front page postcode form
|
|
|
|
|
| |
This is less confusing than redirecting to /auth and then to /my
(as they're logged in). Fixes #1566.
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
Used internally to provide more details about when a priority is applicable.
|
|
|
|
|
|
| |
This lets people filter by multiple categories or states. It uses our
jQuery multi-select plugin to turn the <select multiple>s into little
overlay lists of checkboxes. HTML5 history is also supported.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Inspectors can now tick the optional “Save with a public update”
checkbox, to reveal the “Public update” textarea. This means there is
no longer a need for two separate submit buttons.
|
| |
| |
| |
| |
| |
| |
| |
| | |
IDs and locations at the top, then location-related actions (including
a new “navigate to this problem” button), then status and category
inputs (since these can have an effect on how we display the rest of
the form), then any status/category-related inputs, and finally inputs
for internal details like priority and traffic management.
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| | |
'origin/issues/forcouncils/89-tidy-report-admin-actions'
|
| |
| |
| |
| |
| |
| |
| |
| | |
As part of this, rename "planned reports" to "shortlist".
The `.segmented-control` component now supports basic usage (as in the
admin report actions menu bar) and usage with hidden radio inputs and
labels (as on the report questionnaire page).
|
|/
|
|
|
| |
When a trusted user makes a report in a category that requires inspection, it'll
be sent immediately (i.e. without being inspected first).
|
| |
|
|
|
|
|
|
|
| |
This adds an update field to the bottom of the inspect form, requiring the
inspector to provide an update to be added to the report as it's sent.
See mysociety/fixmystreetforcouncils#64
|