Skip to content

Lock timelogs when project is archived

Niklas van Schrick requested to merge gitlab-community/gitlab:lock-timelogs-when-archived into master

What does this MR do and why?

When a project is archived, most features are locked and read only. This was not the case for timelogs. They could still be added and removed, even when the project was archived.

Before the Timelog UI was implemented, they were locked because they were only manageable with quick actions (and notes are locked in archived state)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

  1. Create a project
  2. Create an issue in that project
  3. Add a timelog to that issue (verify that this still works)
  4. Archive the project
  5. Add a timelog to the issue (verify that this is not possible anymore)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports