Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Shifts/Reports: `locked` field migration

Open
#385 0 comments 0 reactions 1 assignee View on GitHub

@zakriya057 is already working on this.

Since May 14, 2025.

Assessment

This issue has not been assessed yet.

Description

enhancement low-priority

So far the locked field signals whether a month is already locked and the report is archieved in the time vault.

However i have the impression that we should change that so that

  • Migrate Field locked from Shift to Report (Includes data migration sigh)

  • Refactor the validation of ShiftSerializer to check whether the months Report instance is already locked

  • Refactor lock_shifts() Endpoint of ContractViewSet to set locked status on Report rather than shifts

  • Refactor all Querries that access locked field of Shifts to now access locked of Report

Dominant language
Python
Stars
0
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ClockGU/clock-backend

All issues in ClockGU/clock-backend

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.