Create model
Create migration
Create admin interface

This mostly implements #159
Introduce a new field that denotes the timestamp when the plan was published
Introduce admin actions to publish and unpublish the plan and set that timestamp accordingly
Prevent other means to change visibility of the plan
Use that timestamp to only highlight recent changes when they occurred after the plan was already published

Use action with intermediate page instead of direct action for publishing and unpublishing of plans
This allows to create a link on the events detail page and on the status page to change the plans visibility
Add link to detail view
Visualize plan visibility on status page and allow to toggle it from there
This implements the final function of #159

Move loop-based action code to mixin that will only be used when more complex actions should be performed
Use queryset update function on existing actions to perform the necessary updating in only one db call instead of one query per entity
Additionally, visualize manually_resolved status in admin interface of CV

Looks like this was broken since the switch to individual boxes per category.
Fixed it and made it more robust (show error message when trying to export AKs from more than one event at the same time).

Leverage the decorators introduced in django 3.2 for methods that do not use them already

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Add two admin actions to reset interest and interest counter of AKs -- each including a preview/confirmation step
This implements #153

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Add three admin actions to mark CVs as resolved, or set the level to 'warning' or 'violation' -- each including a preview/confirmation step
Introduce a generic view inheriting from the generic admin intermediate view to handle confirmations for admin actions (performing on multiple, freely selected items)
This implements #154

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This allows specifying the parameters without the need to know the GET keys
Also resolve double-compiling issue and thus switch from custom version of django-tex to the latest official release
Minor improvements to generic admin action view
This implements #152

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This adapts submethods of the makemessages command to use generic forward slashes instead of os specific slashes, e.g., backslashes on windows

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This mostly implements #159
Introduce a new field that denotes the timestamp when the plan was published
Introduce admin actions to publish and unpublish the plan and set that timestamp accordingly
Prevent other means to change visibility of the plan
Use that timestamp to only highlight recent changes when they occurred after the plan was already published

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Bump django-split-settings, django-simple-history, django-registration-redux, django-debug-toolbar, djangorestframework, and pytz
Create migration reflecting the changes in simple-history and pytz

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Bump to latest version of Django 3.2
Fix dark theme issue by fixing the order of css imports in admin
Cleanup admin login template (remove copied code as far as possible)

Introduce admin action
Add function to find AKs without availabilities to event model
Link new action on view of AKs requiring special attention
Minor design improvements
This implements the final part of #145

This implements first part of #145

Introduce a new generic view that can be used for all admin actions that require a preview/confirmation or a form to specify parameters
Change AK Orga Message deletion view to use this generic view instead of a manually adapted delete view

Previously, linking of next and previous AKs did not always work correctly for wishes
Also remove input for interest on AK list

Implements #147

Implements #146
Show: AKs with comments, AK wishes with slots, AKs without availabilities, AKs without slots

This implements #140

This implements #129

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Make sure plan is hidden by default and allow to adapt/change this during the usage of the wizard
This fixes #115

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

For admin views of AK (category, requirements), Room (properties), AKSlot (room) the mentioned filters now only show choices related to the current event if such a filter is active at the same time.
This implements #128
Additionally, the filter ordering was adapted for all admin views (event now always shows up first)

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

One can now specify whether there should be symbols for owner and duration of a wish such that the person leading the plenum can write one the slides if some is interested in becoming owner of the AK or not. The default link on the status page hides those symbols.

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This implements #139

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This is part of #123

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Manually trigger post_save signal after bulk create of replacing availabilities
This fixes #132

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This includes returning the edit url as part of the (internal) API response

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

This fixes #130

Benjamin Hättasch authored 2 years ago and Nadja Geisler committed 2 years ago

Make sure event is only loaded once
Massively reduce amount of SQL queries (e.g., plan view reduced from multiple queries per AK where over half of them are duplicates down to only 2 queries -- independent of AK count)
Replace software-side list constructions with in-database operations

Add a new mandatory event reference to the model
Add a migration that makes sure all existing messages are updated accordingly
Adapt the frontend view that sends the message to fill the event field

This endpoint checks for validity of the request and increments the AK interest counter if currently allowed

adds datetimefield for start to Event model
adds datetimefield for start to Event model
adds translations
adds migration