Based on the designs/discussions in the [discovery issue](https://gitlab.com/gitlab-org/gitlab/-/issues/231247) and [backend issue](https://gitlab.com/gitlab-org/gitlab/-/issues/255340), this issue is to track the development of the edit compliance frameworks page. The form should have the following fields: * **Title:** \[ e.g. HIPAA, SOX, Internal, Tech Risk, otherCustomLabelName \] * The labels should allow the use of labels that *look* scoped (use of `::`) but should not implement or leverage any scoped label behaviour for now. * **Description:** \[ e.g. "This label should be applied to projects which are regulated by `HIPAA`" \] * **Pipeline configuration** * **Background color** ## Out of scope: - [Enforcement / "regulated" toggle](https://gitlab.com/gitlab-org/gitlab/-/issues/220190) - Force Merge (under ~"workflow::solution validation") ## Mockups |Settings Page|Edit|New| |---|---|---| |  |  |  | ## Tier The ability to create/edit/assign **custom** compliance labels is a ~"GitLab Premium" feature. ## Feature flag This feature should only be shown if the ~"feature flag" `:ff_custom_compliance_frameworks` is set ## Implementation plan - Create HAML page to edit a framework - Add breadcrumbs - Add title - Add framework form app and add to HAML page, pass framework ID - Add the edit icon button to the list app and redirect to this new HAML page **Thought:** This page requires a GraphQL query to retrieve the form data. Would using `- add_page_startup_graphql_call()` make sense? :thinking: