feat(statuspage): add region hint to statuspage modal message field#257
Merged
Conversation
Add a Block Kit hint below the Message input reminding ICs to specify US1, US2, or 'all US' in statuspage updates so customers know which region is affected. Co-Authored-By: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-Authored-By: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
spalmurray
force-pushed
the
feat/statuspage-region-hint
branch
from
f2a5713 to
25285a6
Compare
taylor-osler-sentry
approved these changes
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Block Kit
hintbelow the Message input in the statuspage modal (both new post and update flows) reminding ICs to specify which US region is affected.The hint reads:
Why
With US2 coming online, a single "US" statuspage update is ambiguous — customers on US1 vs US2 need to know if they're actually affected. This is a low-friction nudge at the exact moment ICs are writing the public-facing message.
Context: discussed in #team-sre as part of US2 region launch prep.
View Session in Sentry