You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
When components / flags selected --> maintain consistency in coverage data across repo overview #1269
What product do you want to improve?
Repo overview page
Is your feature request related to a problem? Please describe.
Right now, when you select certain set of components or flags on a given branch, it's actually not obviously in the file tree what the overall coverage is for the selected set of components or flags
Describe the solution you'd like
I think it would make sense to include a "total" or "sub-total" in the file tree view
Describe alternatives you've considered
Alternatively, we could also have the sunburst, coverage over time and repo coverage numbers update dynamically as components are selected.
If we don't take this approach, we should additionally clarify that the "selected components / flags" are only applicable to the file tree, and not metrics "above the line"
Additional context
Brought up by an enterprise customer
@katia-sentry here's demo/prototype based on the description suggestion. The design can be broken down in different ways and depending on the constraints the page could work together or separately; here are areas it'd be great to look at:
If user applies selection to sunburst, the files match the selection
If filters are applied subtotal of the lines shown, per the component/flag
If either are applied, the summary atop also aligns to the main selection
this could be one part that doesn't coordinate to the selection (remains as repo data)
apply_filters.mov
Could we schedule a design/eng discovery around this one?
Activity
jerrodcodecov commentedon Mar 12, 2024
@codecovdesign seeking an update on ingestion on this matter, thanks!
codecovdesign commentedon Mar 12, 2024
@jerrodcodecov thanks ping, marking
in-discovery, adding to design sprint (upcoming) and will finalize/prep todev readycodecovdesign commentedon Mar 18, 2024
@katia-sentry here's demo/prototype based on the description suggestion. The design can be broken down in different ways and depending on the constraints the page could work together or separately; here are areas it'd be great to look at:
apply_filters.mov
Could we schedule a design/eng discovery around this one?
katia-sentry commentedon Mar 18, 2024
@codecovdesign yes we can schedule a sync for this with @RulaKhaled and @rohitvinnakota-codecov
codecovdesign commentedon Mar 20, 2024
review with @rohitvinnakota-codecov @RulaKhaled 3/20
codecovdesign commentedon Mar 26, 2024
review 2 with @rohitvinnakota-codecov and @RulaKhaled
Next steps are to resolve the bug findings, then revisit the updates to filtering / sunburst etc
vlad-ko commentedon Jun 17, 2024
Do we have any update that I could share with the customers?
codecovdesign commentedon Jun 17, 2024
@vlad-ko it looks like the initial blockers have been addressed; tentatively moving #1453 to
dev readycc @katia-sentrykatia-sentry commentedon Jun 17, 2024
Thanks @vlad-ko @codecovdesign. I've added #1453 to next sprint
nikosatwork commentedon Jun 18, 2025
Hi @vlad-ko @katia-sentry @codecovdesign. I wanted to follow up on this feature. Is there a version available I could test perhaps? Thank you 🙏