Skip to content

feat(nimbus): add analaysis window indicator inside metric name cards#15239

Merged
moibra05 merged 1 commit into
mainfrom
14850
Jun 4, 2026
Merged

feat(nimbus): add analaysis window indicator inside metric name cards#15239
moibra05 merged 1 commit into
mainfrom
14850

Conversation

@moibra05

Copy link
Copy Markdown
Contributor

Because

  • It's often times unclear which analysis window is currently being displayed for a metric's results

This commit

  • Adds a text indicator that tells us which analysis window is being reflected in the main page results

Fixes #14850

@moibra05

Copy link
Copy Markdown
Contributor Author
image

Comment thread experimenter/experimenter/jetstream/results_manager.py Outdated
@mikewilli

Copy link
Copy Markdown
Contributor

There was some recent confusion on what the Overview section of the metric details modal is showing -- can/should we tack something on to this PR to update that too? Or file a new ticket?

@moibra05

Copy link
Copy Markdown
Contributor Author

i think we can just include that change in this pr and broaden the scope/title to covering general improvements to analysis window representation

@moibra05 moibra05 force-pushed the 14850 branch 2 times, most recently from 82bd90e to 4ebfe61 Compare June 1, 2026 17:51
@moibra05

moibra05 commented Jun 1, 2026

Copy link
Copy Markdown
Contributor Author

We discussed how 3DR and 2-week retention should be labeled in the UI. While there was some discussion around whether different time windows (e.g. Overall vs Day 4 for 3DR, Overall vs Week 2 for retention) should be shown, the consensus was to keep this ticket scoped to its original goal: adding a label that reflects the currently displayed window. Any broader changes to retention window semantics can be handled in a follow-up ticket. For the current implementation, we've decided labels such as "Day 4" for 3DR and "Week 2" for retention accurately describe the existing behavior.

@mikewilli mikewilli left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super simple, love it! There are a couple potential scenarios I'd like to avoid that I left comments about. Please feel free to let me know if the concerns are unfounded, otherwise we should ensure we guard against them before merging to avoid potentially displaying incorrect info.

Comment thread experimenter/experimenter/jetstream/results_manager.py
Comment on lines +404 to +408
if (
kpi["slug"] == NimbusConstants.RETENTION_3_DAYS
or kpi["slug"] == NimbusConstants.RETENTION_3_DAYS_DESKTOP
):
kpi["displayed_window"] = "Day 4"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this unnecessary too?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry what did you mean by unnecessary? isn't it still true that 3dr only shows the day 4 window index? if that isn't there the displayed window for it will be either daily, weekly, or overall all of which presumably wouldn't be correct

@mikewilli mikewilli Jun 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh right, I keep forgetting that the label by default is not specific to each metric based on the data that comes in. Ok, let's go with this then.

@moibra05 moibra05 added this pull request to the merge queue Jun 4, 2026
Merged via the queue into main with commit dafa1be Jun 4, 2026
26 checks passed
@moibra05 moibra05 deleted the 14850 branch June 4, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Display which time window each metric is using on results

2 participants