Skip to content

Draft: Resolve "Inherit rules from Group level to Project level"

What does this MR do and why?

  1. Initiate group MR approvals table: create a new component using already existing project level MR approvals table together with Vuex store.
  2. Integrate with backend for GET and POST: create a helper for the app data, create actions for GET and POST
  3. Hides this feature behind an already existing feature flag (introduced in the backend issue that is already merged)

Screenshots or screen recordings

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

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

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

Related to #425181

Edited by Paulina Sedlak-Jakubowska

Merge request reports

Loading