Skip to content

Conversation

@dashed
Copy link
Member

@dashed dashed commented Jan 24, 2026

Closes https://linear.app/getsentry/issue/BIL-2005/add-emerge-billing-overage-ui-with-contact-sales-cta

Summary

  • Add special handling for Emerge data categories (SIZE_ANALYSIS, INSTALLABLE_BUILD) in the navigation billing status component
  • Show "Contact Sales" CTA (mailto:sales@sentry.io) instead of AddEventsCTA since Emerge categories don't have PAYG available
  • Support three scenarios:
    • Only Emerge categories exceeded → Contact Sales CTA
    • Both Emerge and standard categories exceeded → Both sections displayed
    • Only standard categories exceeded → Original AddEventsCTA behavior
Screenshot 2026-01-24 at 4 16 39 PM

Test plan

  • Added tests for Size Analysis quota exceeded with Contact Sales CTA
  • Added tests for Build Distribution quota exceeded with Contact Sales CTA
  • Added tests for both Emerge categories exceeded together
  • Added tests for mixed Emerge and standard categories exceeded
  • All 21 tests in navBillingStatus.spec.tsx pass
  • Manually verified UI in dev environment with mocked database changes

@linear
Copy link

linear bot commented Jan 24, 2026

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jan 24, 2026
@dashed dashed self-assigned this Jan 24, 2026
Add special handling for Emerge data categories (SIZE_ANALYSIS, INSTALLABLE_BUILD)
in the billing status alert:

- Show Emerge-specific copy explaining quota exceeded status
- Display "Contact Sales" CTA instead of standard AddEventsCTA (since Emerge
  has no PAYG/on-demand option)
- Use dynamic quota value from subscription.categories instead of hardcoded value
- Handle mixed scenarios (Emerge + other categories exceeded)

BIL-2005
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants