getsentry / getsentry/sentry

Keep consistent time-range selection between error graph views

Open
#102,718 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### 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).
Image

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.

Image

### 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=` or `start=` 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

Contributor guide

Open the contributing guide

Research direction

Review the issue feed, its mini stats graphs, and the individual issue page, focusing on how their time ranges are represented in URL parameters. Trace the existing groupStatsPeriod, statsPeriod, and start behavior first. Done means the selected feed range consistently carries into the graphs and issue page without manual reselection.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.