Skip to content

VSD - Comparison panel - [FE] adding panel-level "filter by label"

Release notes

Enhancing flexibility and customization to the Value streams dashboard.

A new configuration file was added to the Value streams dashboard to allow easy customization of the dashboard's behavior and appearance. This file enables users to define various settings and parameters such title, description, number of panels and filters. It be managed with version control systems like Git. This enables tracking and maintaining a history of configuration changes, reverting to previous versions if necessary, and collaborating effectively with team members.

With the new Filters by labels, users can now customize their views according to their specific needs and preferences.They can adjust the metrics comparison panel based on their areas of interest, filter out irrelevant information, and focus on the data that is most relevant to their analysis or decision-making process.

Overview

Following this feedback, we need to add label filters to the Metrics comparison panel.

Proposal

  1. Extended the Metrics comparison configuration file schema with option to filter by labels.
  2. If a metric does not support the filter Label filters return null for the metric (i.e. filter the metric out).
  3. Metrics need to be filtered by one label, or multiple labels.
  4. If the data on the panel has filter by label - the UI will have an indication about the label - see design.
  5. Panels configured with the "filter by label" option will only show metrics that support "label filtering".
  6. Adding text in the config file and in the UI via info icon (i) with this explanation: "You can use the "Filter by label" option only with metrics that support label filtering. To learn more, see the Value streams dashboard documentation."
  7. An error message should be displayed if admins add metrics that don't support label filtering. Error message text: "The following metrics can't be filtered: [tell which metric(s) have been added that don't support filtering]. To learn more check out the Value stream dashboard documentation."
  8. Both Projects and Groups.

Mockup example:

Screenshot_2023-05-01_at_15.59.31

Proposed schema

data:
  # Currently supported
  type: metrics_comparison
  namespace: {GROUP_OR_PROJECT_NAMESPACE}

  # Add support for
  filter_labels:
    - bug
    - severity2 
    - customer
    - section::dev

Next iteration:

Design source

🖼 Figma page →

Metrics that support filter by label:

  1. Lead time
  2. Cycle time
  3. New issues
  4. Closed issues
  5. MR Throughput

Old suggestion

Click to expand 
filter_labels:
        - Lead time / bug 
        - Lead time / feature 
        - Lead time / maintenance 
        - Lead time / bug AND priority1
        - Lead time / feature AND priority1
        - Lead time / maintenance AND priority1 
        - MR Throughput / bug
        - MR Throughput / feature
        - MR Throughput / maintenance
## Open questions - [ ] What if the project does not have any labels? - [ ] How will panel level filtering work together once we introduce a global filtering? - [x] Should we be able to drill into a specific projects and compare those?

Resources

Edited by Haim Snir