Currently regression tracking is only supported for one view per release. We believe the main reason is to be able to support showing regressions / triage records for adhoc queries that are not associated with a view. Additionally as we navigate through the UI we loose information regarding which view we are navigating from.

We previously hit the issue where we changed the dbgroupby clause associated with our main view and lost all regressions / triage records because of it.  TRT-2274 was opened to review the design. We may need to re-prioritize that spike to suggest a design to accomplish the goals in this card.

• We need to be able to track regressions across multiple views for the same release
• We should be able to triage those regressions
• We should not have to duplicate regressions / triage records for regressed tests that overlap between views
• When using cross compare it would be nice (stretch goal) to be able to see regressions / triage records for the basis variant being cross compared (this could be a separate UI and not applied to the test details by default) as a helper to identify regressions / triage entries already known.