Skip to content

Change UX flow for compliance framework in security policies

Artur Fedorov requested to merge 432222-policies-policy-scope-stay-open into master

What does this MR do and why?

This MR changes flow for compliance framework

After this change, dropdown for compliance frameworks stays open after new framework is created

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

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

Description Video
Dropdown stays open when framework is created open framework.mov

How to set up and validate locally

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

  1. Enable Feature Flag

    Feature.enable(:security_policies_policy_scope)
    1. Go to Settings -> General
    2. Toggle the Permissions and group features section
    3. Enable Security policy scope
    4. Go to a Group -> Secure -> Policies -> New policy -> New scan result/execution policy -> check Policy scope section is there.
    5. Try to create new compliance framework from dropdown
    6. Make sure dropdown is open after framework is created

Related to #432222 (closed)

Edited by Artur Fedorov

Merge request reports