Keep consistent time-range selection between error graph views

[joeyjackson]

Problem Statement

A very common pattern with usage of sentry is to correlate an incident with a spike in errors using the graph trendlines. However, this is sometimes difficult/unintuitive the time range selected in the issue feed does not automatically propagate to other trendline graphs as you drilldown into an issue. For example, when you select a time range in the issues feed, the mini stats graphs on the issues results by default have the time range of 24h instead of the selected time range (it is unintuitive to have to change that).

Also when you select an issue from the results, the time range on the individual issue page defaults to "Since first seen"/90d instead of the time range from the issues feed. This can be confusing/annoying to then have to reselect the time range you are interested in.

Solution Brainstorm

It would be great if the time range propagated through views most likely through url parameters.

For the first case (issue feed), if you select the time range that matches the selected one on the mini graphs, sentry adds the url param groupStatsPeriod=auto which seems to do what I want. It would be great if this option was the default or there was a setting to make it the default for a project/org.

It is also possible to add the url param statsPeriod=<duration> or start=<timestamp> on the individual issue page to have it pre-select a time range. We could have the issue feed automatically add these params when selecting an issue to match the time range from the selection in issue feed.

Product Area

Unknown

[linear]

ENG-5826

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[roggenkemper]

can't speak to the first point, but the second was an intentional decision to give more context to the lifetime of the issue. definitely seems like there's some room for improvement here so adding it to the team's backlog