| Commit message (Collapse) | Author | Age | Lines |
... | |
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
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.
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| | |
Instead of returning all templates for the problem's body, return those
for the problem's category (or with no category).
|
|/
|
|
| |
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.
|
| | |
|
|/
|
|
|
| |
It would always create a new report rather than return an existing one,
if present.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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
|
| |
|
|\ |
|
| |
| |
| |
| | |
Allow get_extra_metadata to return all the data with no argument.
|
|/
|
|
|
|
|
| |
This is a cut-down version of the full inspect screen.
We truncate the co-ordinates just in case (they should be anyway but
e.g. the test report isn't).
|
|
|
|
|
|
|
| |
This moves the response priority values from a cobrand-specific method to a full
DB model, and includes management screens in the admin for administering them.
For mysociety/fixmystreetforcouncils#66
|
|
|
|
|
|
|
|
|
|
|
| |
Categories can now require reports to be marked as 'inspected' via the frontend
before they're sent by send-reports.
A side-effect here is that send-reports will perform an extra n queries for each
report, where n is the number of bodies that report is being sent to, but
hopefully in practice this won't matter as it's an offline cronjob.
See mysociety/fixmystreetforcouncils#50
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This builds on the response templates in the Zürich cobrand:
- Allow response templates to be assigned to categories
- Also adds a auto_response flag, which will be used to automatically create
updates when reports are made.
- Include response templates select box on update form
For mysociety/fixmystreetforcouncils#31
|
| |
|
| |
|
|
|
|
|
|
| |
A user with the appropriate permission can add/remove reports from their
list of planned reports using a button on a report page. The list can be
viewed at /my/planned.
|
| |
|
|
|
|
|
|
|
|
| |
The 'user_edit' permission is required to edit users.
The admin pages on UK council cobrands only allow editing of users whose
from_body is the same as the logged-in user, or who have sent reports or updates
to the council.
|
| |
|
| |
|
| |
|