| Commit message (Collapse) | Author | Age | Lines |
... | |
|\
| |
| |
| | |
'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).
|
|/ |
|
|\ |
|
| |
| |
| |
| | |
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
|
|
|
|
|
|
|
|
| |
This introduces a new `is_council_with_case_management` flag for Cobrands, that,
when active, considers any report that's been confirmed as having been received
by the Council in question.
See mysociety/fixmystreetforcouncils#65
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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 'created' and 'state' column names are shared between the 'problem' and
'comment' tables, and this was causing ambiguous column references in the SQL.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows users who have the correct permissions to add reports on
behalf of the body or another user.
We enable editing of the email box by default, so that if JavaScript
isn't available, someone can still change the email for the 'another
user' option.
For mysociety/fixmystreetforcouncils#10 and
mysociety/fixmystreetforcouncils#11
|
|/
|
|
| |
Also don't fetch tiles if running tests.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Adds is_superuser flag to User
- Logged-in user must be a superuser or have from_body set in order to access
anything within /admin
- has_permission_to on a superuser will always return true
- Only superusers can create/grant superusers
- New `createsuperuser` command for creating superusers
|
|
|
|
|
|
|
|
|
| |
When viewing a report on FMS.com whose recipient council has a
FMS cobrand, turns the council name into a link to view the same report
on that council's cobranded site.
Includes methods cribbed from Hakim's Open311 refactor branch from
commit 47daa02420a4f5a4264c31efcf2a2e8611c2f23e.
|
|
|
|
|
|
|
|
|
| |
When viewing on FMS.com a report made via a council cobrand, this
adds a link to the FMS for Councils page for more info.
This works by breaking out the report meta line ('Reported in the
Street lighting category by Joe Bloggs at 09:51, Tuesday 1 March 2016')
into its own template which can be overridden for the fixmystreet.com cobrand.
|
|
|
|
|
|
|
|
|
|
|
| |
- Use new `getLocation95` method for geocoding addresses
- Replace Coordinates::CH1903 with Coordinates::CH1903Plus
- Refactor Map::Zurich to use WMTSBase instead of duplicating code
- Slightly refactor map templates to make using custom WMTS tiles easier
- Use correct sizes for marker pins on maps
Closes mysociety/FixMyStreet-Commercial#769.
Closes mysociety/FixMyStreet-Commercial#768.
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Fixes #694.
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
Store image type along with hash in photo column, and use that when
outputting images / generating URLs. Make sure all public photo URL
generation goes through appropriate functions, and change temp URLs
so the filename can be output directly from the list.
|
|
|
|
|
| |
The form element contains 'fixed', so we need to strip the user/council
part of the actual state. Fixes #1369.
|
| |
|
|
|
|
|
| |
If a user is logged in, use their last report/update to set the default
anonymity state.
|
|
|
|
| |
Fixes #1337.
|
| |
|
|
|
|
|
|
| |
There might be the odd update alert we are interested in (those not
auto-signed up for as part of report or update creation), but they
will be rare.
|
| |
|
|
|
|
|
| |
Remove get_photo_params, which only looked at the first photo,
make explicit when we're doing that using `.first`.
|
| |
|
|
|
|
| |
Fixes #1305.
|
|
|
|
|
|
| |
Use a separate attribute for data direct from a database row when
creating a PhotoSet, so that data will always contain one or more
photo IDs.
|
|
|
|
|
|
|
|
|
|
|
|
| |
5c79337 simplified a bit too far, as after then a particular cobrand
could in Nearby and My only filter reports to a particular body, not
any other criteria. To fix this, introduce more generic functions in
the default cobrand to allow more flexibility.
Make sure a few tests delete their bodies fully so that new tests
pass when run as part of the suite.
Fixes #1289.
|
|
|
|
| |
Maintain old location wrappers.
|
| |
|
|
|
|
| |
And create default cobrand class without all of Moose.
|