How to use common features on the Flags UI?

Introduction

This guide explains how to use the common features available in the Flags UI in the Cubyts platform. These features allow teams to control how flags are viewed, filtered, grouped, and configured—helping reduce noise, surface meaningful risks, and focus on what matters most across the SDLC.

Prerequisites

• Access to a Cubyts workspace

• Permission to administer/edit flags

Step-by-Step Guide

Step 1: Control Your View Using “View By”

• In the Flags UI, use the View By option to change how flags are organized.

• You can view flags by:

  • Drift type – Process, Feature, or Code

  • Classification – Planning & Requirements, Development & Quality, Security & Compliance, Deployment & Operations

This flexibility allows teams to quickly switch perspectives based on the type of drift or SDLC dimension they want to focus on.

Step 2: Apply Filters to Narrow Down Flags

• Open the Filter panel to refine the flag list.

• Flags can be filtered using multiple dimensions, including:

  • Flag frequency

  • Epic

  • Sprint

  • Classification

  • Flag type

  • Priority

Filters can be combined to focus on specific scenarios, such as:

• High-priority flags in the current sprint

• Recurring flags associated with a specific epic

This makes large flag lists easier to manage and analyze.

Step 3: Group Flags for Better Readability

• Use the Group By option to organize flags into logical clusters.

• Flags can be grouped by:

  • Project

  • Feature

  • Workflow

  • Work item

  • Assignee (for example, Jira assignees)

Grouping helps teams quickly identify patterns and ownership, such as which assignees or repositories are driving recurring risks.

Step 4: Identify Patterns and Ownership

• Grouped views make it easier to:

  • Spot recurring issues

  • Understand where risks are concentrated

  • Identify accountable teams or individuals

This supports faster prioritization and targeted governance actions.

Step 5: Manage Flag Configuration and Visibility

• From the Flags UI configuration screen, teams can:

  • Enable or disable specific flag types

  • Control visibility across the workspace

  • Customize flag behavior

• Flags can be filtered and managed by categories such as:

  • Process

  • Feature

  • Code

  • Audit-relevant

  • AI-generated

  • Custom-created flags

This allows governance checks to be aligned with internal standards and relevance.

Step 6: Apply Configuration Changes Consistently

• Any configuration changes made in the Flags UI:

  • Apply consistently across the workspace

  • Take effect after the next sync cycle

This ensures controlled, predictable governance without unexpected behavior changes.

Best Practices

• Use View By to switch between risk type and SDLC dimension perspectives.

• Combine filters to isolate the most critical and recurring issues.

• Use grouping to understand ownership and systemic risk patterns.

• Periodically review flag configuration to keep governance aligned with evolving delivery standards.

Conclusion

The common features in the Flags UI—viewing, filtering, grouping, and configuration—give teams the flexibility to explore delivery risks effectively and focus on what matters most. By adapting these controls to your organization’s standards, you can ensure that Flags in Cubyts remain actionable, relevant, and aligned with your governance goals.

Video link: https://www.loom.com/share/8e23915ed2824600a43b25d508ef8696