Introduce model (including migration and admin interface)
Integrate into new event wizard
Display as property in details representation (e.g., used in scheduler)
Allow to choose types in AK add/edit forms
Show type info on AK detail page and in overview table
Adjust tests (including new tests for requirement and type visibility in submission form)
Update translations

Create overview page
Link in admin AKOwner list and in change view, showing the number of AKs by user
This implements #207

Benjamin Hättasch authored 10 months ago and Nadja Geisler committed 10 months ago

Introduce new field
Create migration
Show in admin
Show in message tables on status page
This implements #213

Add or complete docstrings
Remove code smells
Disable irrelevant warnings
Update translations to changed line numbers and line breaks
Move duplicated code for event field pre-population and event timezone adaption to mixins

Move AKModel views into several subfiles to improve overview and resolve problems with circular imports
Introduce new modular status page handling (widgets and views)
Port main status page to new structure
Move AK messages status page visualization to AKSubmission (therefore, they automatically do not show up when there is no possibility to create them)
Introduce status widget for virtual rooms
Fix timezone issue for rendering of AK messages on status page
Adapt status page URL in several views and tests

Benjamin Hättasch authored 1 year ago and Nadja Geisler committed 1 year ago

This way, the frontend views will be used when AKSubmission is installed and active, or otherwise the link to the built-in AK edit form in backend
This reduces the coupling between AKSubmission and other apps that previously needed that app
Use that new property in all places where previously an URL to the submission view was used (for consistency and to allow changes in one place in AKSubmission, too)
This implements #166

Use One2One relationship instead of inheritance
This allows to add and also remove the virtual features of a room

Introduce new model
Create migrations to migrate from existing to new model + a squashed version knowing only about the new model for fresh installations
Adapt admin views
Add django-betterforms as dependency to simply create a form allowing to generate rooms with optionally a virtual component in a single view and create that form
Add view to create rooms in that view and use instead of default django creation form
Use the new name/structure in templates
Move RoomForm to forms.py to make imports easier
Update batch creation of rooms

This resolves #150 and also resolves #179 since now rooms and virtual rooms (rooms with virtual features) are created using the same view

This remove the AKTags model and its usage in views, forms, templates, translations, and backup script
This implements #164

Make sure the more useful local times are displayed both in the form and on the list page

This implements #156

Create new view (including template and form)
Link on status page
Add translations

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 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

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

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)

This implements #126

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

Additionally fix wrong app installed check for ak detail link (should be AKSubmission, not AKScheduling)

Additionally fix wrong app installed check for ak detail link (should be AKSubmission, not AKScheduling)

Create template for slides
Add view
Link view from status page
Update translations

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

Restrict choices (foreign keys & m2m) in admin forms to other objects of the event of the edited instance

Additionally, improve how requirements are shown for AK admin (multiple checkboxes instead of multiselect widget)

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

This reduces the amount of queries from over 450 for a full list (100 entries) to about 50, resulting in a drop of execution time from about 20 seconds to less than one second
This fixes #106

The wizard is used instead of the normal built-in creation workflow
It consists of multiple steps to specify the most fundamental settings (especially the timezone), further settings, copying AKCategories and AKRequirements from existing events and activating the event once the basic configuration is done
The steps after the creation (first two steps) can be skipped

Benjamin Hättasch authored 4 years ago and Nadja Geisler committed 3 years ago

This view can be used to sort aks into tracks using drag and drop. You can also create new ak tracks or delete them.

Add js dependency for drag and drop of lists.
Activate add, update, delete methids to AKTrack API and update method to AK API.
Add and link (on status page) new admin view for management.
Add tags list property to AK model.
Introduce translations for AKScheduling app.
Update translations.

Add new view
Link on status page