### Problem to solve Some audit events are named `audit_operation`. This isn't a descriptive name and makes it difficult to differentiated from other events. Additional context is available in this [epic](https://gitlab.com/groups/gitlab-org/-/epics/8497) and in the [parent epic](https://gitlab.com/groups/gitlab-org/-/epics/8572). ### Proposal Add a meaningful `name` for the following events and actions that can be used to differentiate them from other events: | Event | Action | Location | | ------ | ------ | ------ | | `Create group link` | `Create` | [file](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/services/ee/projects/group_links/create_service.rb) | | `Update group link` | `Update` | [file](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/services/ee/projects/group_links/update_service.rb) | | `Delete group link` | `Delete` | [file](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/services/ee/projects/group_links/destroy_service.rb) | Naming should follow the `noun_verb` format and use the past tense. For example `ci_variable_created`. For events created with `audit_changes` we can pass the event name using the `event_type` argument. ```rb audit_changes(:email, as: 'email address', event_type: 'email_address_added') ``` Consider [this MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92074) as an example of how to do this. ### Implementation plan 1. Add an meaningful event `name` for the events in the `Group Links` model listed in the proposal. - The name should follow the `noun_verb` format. 1. Update the associated specs. ## Notes - [For instructions on how to setup your development environment.](https://about.gitlab.com/community/contribute/development/#setup-the-development-enviroment) - For any questions regarding audit events reach out to a member of the [compliance group](https://about.gitlab.com/handbook/engineering/development/dev/manage/compliance/#group-members).