Feature request: filter builds used to update widget

[epitomus]

We use a single build definition for short lived feature branches as well as master, but this causes reporting problems:

• Branch builds fail more often, and this causes downtime for the widget (message: No code coverage details found for this build definition)
• We only want to show the coverage metrics from master on the dashboard

Ideally we would be able to specify a pattern that is checked before the coverage data is updated for either the branch / PR it's related to, or the build name. E.g. in the following we would want to specify master as the branch, or any build under this definition ending in -Dev

[rafaelfonte]

@sdavis3 are there currently plans to have this branch filtering config in place?

[tvargova]

@sdavis3 We are running into a similar issue - this widget is helpful to visualize the code coverage, we appreciate the possibility to display Branch code coverage, but we're running into reporting problems as it's not giving any “filtering mechanism” that could enable us to select only the appropriate release/git branch/tags etc... it just takes the last run of pipelines for the repo. Is there a plan to enhance the widget with a filtering option?