Lock access for editing of validity range after validity range changes to published status

needs to be ensured with all connected models

marked this issue as related to #10 (closed)

changed the description

added part::backend part::frontend labels

changed milestone to /AlekSIS%"[NLnet #1 (closed)] Fix existing bugs with new timetable"

assigned to @hansegucker

created branch 4-lock-access-for-editing-of-validity-range-after-validity-range-changes-to-published-status to address this issue

mentioned in merge request !44

added prio::1 label