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

Upgrade django to 4.1
Upgrade django-timezone-field, django-simple-history, django-debug-toolbar and django-bootstrap-datepicker-plus
Upgrade mysqlclient
Remove obsolete pytz
Adapt timezone handling code to new interface of TimezoneInfo (part of python since 3.9 and backport included in 3.8)
Drop support for python 3.7 (since Django 4 requires >= 3.8)

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

Add flag (default value true)
Use for wiki export
Add migration, translation & test
This implements #178

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

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

Create model
Create migration
Create admin interface

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

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

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

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

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

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

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

Both violation and warning for capacity nearly exceeded
Adapt model (better description for capacity exceeded violation type)
Add comment to detail fields of constraint violation

Use for slide generation
Show effect it will have on AK detail page
Add migration
Add translations

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

Previously, ak and ak slot sets were modelled as class attributes, which could cause wrong AKs to show up in a relation when multiple constraints were updated in the same function call

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

Improve constraint violation string representation to prevent endless recursion
Create violation check for changed owner of AK (bound to new m2m_changed signal)
Add doc comments

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

Add helper fields and methods to ConstraintViolation model
Introduce helper method do determine whether two AKSlots overlap
Add receivers to AKScheduling
Implement stub for OWNER_TWO_SLOTS violation

Previously, ak and ak slot sets were modelled as class attributes, which could cause wrong AKs to show up in a relation when multiple constraints were updated in the same function call

Improve constraint violation string representation to prevent endless recursion
Create violation check for changed owner of AK (bound to new m2m_changed signal)
Add doc comments

This implements #126

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

This also introduces some additional properties for human readable details of the violations to the model

Add helper fields and methods to ConstraintViolation model
Introduce helper method do determine whether two AKSlots overlap
Add receivers to AKScheduling
Implement stub for OWNER_TWO_SLOTS violation

This also introduces some additional properties for human readable details of the violations to the model

Also use this representation in durations list of AK

Previously, a slot duration of exactly one hour was shown as "1: 0" instead of "1:00"

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.

This fixes #97
Exclude interest_counter from AK history
Prevent saving of history record when increasing interest counter

Run the following action after applying the change/migration to remove existing duplicate history records (the ones without changes to tracked fields, hence caused by either saving without changing any field or especially the ones created due to changes of the now ignored interest_counter):
python manage.py clean_duplicate_history AKModel.ak

Use more pythonic way to calculate times and construct strings

Add new Strings + Translations
Fix Typos
Remove event specific vocabulary