Skip to content

Conversation

@evanpurkhiser
Copy link
Member

NEW-564: There needs to be some way to mute the entire cron detector

Since muting now operates at the environment level, disallow muting a monitor when it has no environments (as it would do nothing). Shows a helpful tooltip explaining that muting is only available when there are monitor environments.

Important

Not to be merged until the backend components are all released

[NEW-564: There needs to be some way to mute the entire cron detector](https://linear.app/getsentry/issue/NEW-564/there-needs-to-be-some-way-to-mute-the-entire-cron-detector)

Since muting now operates at the environment level, disallow muting a monitor
when it has no environments (as it would do nothing). Shows a helpful tooltip
explaining that muting is only available when there are monitor environments.
@evanpurkhiser evanpurkhiser requested a review from a team as a code owner November 18, 2025 22:32
@evanpurkhiser evanpurkhiser requested review from a team and removed request for a team November 18, 2025 22:32
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 18, 2025
muteDisableProps.title = t(
'Muting is only available when there are monitor environments'
);
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Bug: UI Masks True Reason for Disabled Button

When a monitor has no environments, the muteDisableProps.title is unconditionally overwritten, which loses the permission tooltip if the user lacks edit access. When both conditions are true (no permission and no environments), users see the environment message instead of the permission message, masking the actual reason the button is disabled.

Fix in Cursor Fix in Web

Copy link
Member Author

Choose a reason for hiding this comment

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

I think that's OK

Copy link
Contributor

Choose a reason for hiding this comment

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

agree - the user can fix the env, then the permissions error will show up. might be nice if you could see both, but doesn't seem vital.

Copy link
Member Author

Choose a reason for hiding this comment

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

Well it would be, the user creates an env, then they see they can't mute the monitor.

either way doesn't matter, this will go away in the future

@evanpurkhiser evanpurkhiser changed the title ref(crons): Disable mute button when monitor has no environments ref(crons): Disable mute button when monitor has no environments (stage 5) Nov 18, 2025
@evanpurkhiser evanpurkhiser enabled auto-merge (squash) November 19, 2025 19:52
Copy link
Contributor

@saponifi3d saponifi3d left a comment

Choose a reason for hiding this comment

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

:shipit:

muteDisableProps.title = t(
'Muting is only available when there are monitor environments'
);
}
Copy link
Contributor

Choose a reason for hiding this comment

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

agree - the user can fix the env, then the permissions error will show up. might be nice if you could see both, but doesn't seem vital.

@evanpurkhiser evanpurkhiser merged commit 7d1bb9f into master Nov 19, 2025
49 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/ref-crons-disable-mute-button-when-monitor-has-no-environments branch November 19, 2025 22:21
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.

3 participants