WIP: Draft: Resolve "Lock access for editing of validity range after validity range changes to published status" #132

Draft
hansegucker wants to merge 0 commits from 4-lock-access-for-editing-of-validity-range-after-validity-range-changes-to-published-status into master
Owner

Closes #4

Closes #4
Member

@hansegucker are you planning to do this (or to give it to someone)?

@hansegucker are you planning to do this (or to give it to someone)?
Member

@hansegucker ?

@hansegucker ?
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 4-lock-access-for-editing-of-validity-range-after-validity-range-changes-to-published-status:4-lock-access-for-editing-of-validity-range-after-validity-range-changes-to-published-status
git switch 4-lock-access-for-editing-of-validity-range-after-validity-range-changes-to-published-status
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
aleksis/AlekSIS-App-Lesrooster!132
No description provided.