When running pipelines tailored to specific domains, environments, or regional targets within a single repository, identifying the specific context of a run requires digging into workflow details or individual job logs. While our immediate use case involves distinguishing pipelines by jurisdiction (e.g., region/country), this applies broadly to any pipeline metadata.

Proposed Solution

Introduce a native label (or tags) parameter in the .circleci/config.yml at the workflow level. This label should be rendered prominently in the main Pipelines UI view and provide filtering capability in the dashboard.

While region/country is a primary example, workflow labels could be used for any custom categorisation, such as:

Target Jurisdiction / Region: US, EU, APAC

Environment: staging, production, sandbox

Test Scope: e2e, smoke, performance

Component / Microservice: auth, billing, notifications

Example Configuration (.circleci/config.yml):

workflows:

run-system-tests:

label: US # Proposed key-value or simple string tag

jobs:

- run-tests

UI Mockup / Expected Behavior

Pipeline List View: Display a badge next to the commit/pipeline details showing the defined label (e.g., US).

Filtering: Allow users to filter the Pipelines view by label or tag values to quickly locate regional test runs or specific deployment targets.