Implement Experimental Banners for Advanced Security Policy Editor

Background

We need to implement experimental banners to allow users to opt-in to the new advanced editor for security policies. This will enable us to collect feedback from internal users and select customers before a wider rollout.

Implementation Requirements

  • Create a banner/toggle system similar to the "new issue look" toggle
  • Allow users to enable/disable the advanced editor UI
  • Ensure the feature is behind a feature flag for controlled rollout
  • Include clear messaging about the experimental nature of the feature

Banner Design

  • Implement a non-intrusive banner at the top of the security policy editor
  • Include toggle mechanism to switch between current and advanced editor
  • Consider responsive design requirements (estimated 1 week max for implementation)
  • Note: The current design has grey bars (low-fidelity) and a grabber to move left/right that could be improved

Potential idea how this could look like: image

Rollout Plan

  1. Phase 1 (18.2): Enable feature flag for:

    • Internal GitLab users
    • Select customers who understand they're testing an experimental feature

  2. Phase 2 (18.3): Collect and analyze feedback

    • Make decision on whether to proceed or conduct more extensive testing

  3. Phase 3 (18.3/18.4): If feedback is positive:

    • 1 week for UI polish based on feedback
    • Move to formal experiment with wider audience

Feedback Collection

  • Create a structured feedback form with specific task-based questions
  • Focus on:
    • User understanding of the interface
    • Perceived usefulness of the advanced editor
    • Interaction model effectiveness
    • Any usability issues encountered
  • Provide clear link for submitting feedback

Design Considerations

  • Review existing design language for consistency
  • New UI elements can be created if needed
  • Consider future inclusion in the design system if appropriate

Timeline

  • Implementation ready by 18.2
  • Feedback collection by 18.3
  • Decision point at end of 18.3
  • Formal experiment in 18.3/18.4 (if approved)

Success Criteria

  • Users understand the interface
  • Users find the advanced editor useful
  • No major usability concerns identified
  • Clear path forward for wider implementation or necessary improvements
Edited by Alan (Maciej) Paruszewski