Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #301124
Closed
Open
Issue created Feb 04, 2021 by Tan Le@tancnle👣Contributor0 of 6 checklist items completed0/6 checklist items

Audit Events: Add merge request settings changes part 1

Problem to solve

Changes to project merge request settings could cause considerable impact. We would like to track these settings changes in audit events and potentially enable more automation around this area.

Intended users

  • Cameron (Compliance Manager)
  • Sasha (Software Developer)

User experience goal

Users can view audit events related the merge request settings changes under Project > Security & Compliance > Audit Events.

Proposal

Capture audit events when users modify merge request settings via app and API

  • Merge method
  • Merge options
  • Squash commits when merging
  • Merge checks
  • Merge suggestions
Screenshot

Screen_Shot_2021-02-05_at_12.30.31_am

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

GitLab Premium

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

  • Current tracking of project changes is done via Project::UpdateService
  • Existing audit tracking results in a lot of unnecessary inserts. Every field change create one insert statement. We can leverage on the new Audit::Auditor to do a bulk insert.
Edited Apr 13, 2022 by Sam Kerr
Assignee
Assign to
Time tracking