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,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • 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
  • #357021
Closed
Open
Issue created Mar 28, 2022 by Zamir Martins@zmartinsDeveloper6 of 13 checklist items completed6/13 checklist items

List scan result policies under project settings approvals

Why are we doing this work

As an administrator for GitLab, I need to be able to see all of the merge request approval rules in a single location so that I can understand everything that will be required for an MR to be approved.

Relevant links

Design
Scan result policies
Approval rules

Non-functional requirements

  • Documentation:
  • Feature flag:
  • Performance:
  • Testing:

Implementation plan

  • backend Update payload to include path to security policies.
  • frontend Add securityPoliciesPath (previous item) and projectPath(existing) into provide in order to be accessible by the new component. Related code.
  • frontend Render the list of scan result policies between project rules and approval settings.
  • frontend Load scan result policies via graphql.
  • frontend Join branches (from all rules) as discussed here.
  • frontend Humanized policy text should use the existing format as discussed here.
Edited Apr 20, 2022 by Zamir Martins
Assignee
Assign to
Time tracking