<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> Accurately tracking GitLab events on an instance is a security feature and is of critical importance for enterprises, especially ones that operate with strict traceability requirements. While we currently track certain events in Audit Events, our goal should be to record ~100% of events for administrators and auditors to evaluate in a single source of truth. This epic covers project-level settings changes. Items in the following list are missing from audit events, and should be added: #### Missing events in project settings and activities: 1. General 1. [ ] Project tags - https://gitlab.com/gitlab-org/gitlab/issues/5246 1. [ ] Avatars and project description - https://gitlab.com/gitlab-org/gitlab/issues/8056 1. [ ] Permissions - https://gitlab.com/gitlab-org/gitlab/issues/8057 1. [ ] Default issue description template - https://gitlab.com/gitlab-org/gitlab/issues/8064 1. [ ] Merge request settings - https://gitlab.com/gitlab-org/gitlab/-/issues/301124 1. [x] Merge request approval settings and rules - https://gitlab.com/gitlab-org/gitlab/-/issues/7531 1. Only allow merge requests to be merged if the pipeline succeeds 1. Only allow merge requests to be merged if all discussions are resolved 1. [x] Default merge request description template - https://gitlab.com/gitlab-org/gitlab/issues/8065 1. [ ] Automatically resolve merge request diff discussions when they become outdated (is this necessary?) 1. [ ] Show link to create/view merge request when pushing from the command line (is this necessary?) 1. [ ] Merge request merge strategy - TBD 1. [x] Approvers list - https://gitlab.com/gitlab-org/gitlab/issues/7531 1. [x] Approvers required - https://gitlab.com/gitlab-org/gitlab/issues/7531 1. [ ] Service Desk - https://gitlab.com/gitlab-org/gitlab/issues/8075 1. [ ] Badges - https://gitlab.com/gitlab-org/gitlab/issues/8066 1. [x] Export project - https://gitlab.com/gitlab-org/gitlab/issues/4550 1. Members 1. [ ] Invite group - https://gitlab.com/gitlab-org/gitlab/issues/205 1. Integrations 1. [ ] Webhook additions/removals - https://gitlab.com/gitlab-org/gitlab/issues/8068 1. [ ] Project service additions/removals - https://gitlab.com/gitlab-org/gitlab/issues/8068 1. Repository 1. [ ] Default branch - https://gitlab.com/gitlab-org/gitlab/issues/8069 1. [ ] Push rules - https://gitlab.com/gitlab-org/gitlab/issues/8069 1. [ ] Mirroring - https://gitlab.com/gitlab-org/gitlab/issues/8069 1. [x] Protected branches - https://gitlab.com/gitlab-org/gitlab/issues/1487 1. [ ] Protected Tags - https://gitlab.com/gitlab-org/gitlab/issues/8069 1. [ ] Deploy Keys/Tokens - https://gitlab.com/gitlab-org/gitlab/issues/8069 1. CI/CD 1. [ ] https://gitlab.com/gitlab-org/gitlab/issues/8073 1. Actions 1. [x] Push git actions - https://gitlab.com/gitlab-org/gitlab/issues/1411 1. [x] Repo download - https://gitlab.com/gitlab-org/gitlab/issues/4550 1. [ ] Pull git actions - https://gitlab.com/gitlab-org/gitlab/-/issues/384960 1. [ ] Push container registry actions 1. [ ] Pull container registry actions 1. Compliance pipelines 1. [ ] Compliance framework label changed - https://gitlab.com/gitlab-org/gitlab/-/issues/329362