search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.6k stars 4.13k forks source link

can't add or remove teams from cron monitors #69589

Open JeremiaAu opened 4 months ago

JeremiaAu commented 4 months ago

Self-Hosted Version

24.4.1

CPU Architecture

x86_64

Docker Version

26.1.0

Docker Compose Version

2.26.1

Steps to Reproduce

  1. Navigate to "Crons"
  2. Click on a random existing monitor
  3. Click on "Edit"
  4. Add a new team and remove the old team from the notifications section.
  5. Click on "Save Changes"
  6. Click on "Edit"

Expected Result

Only the newly chosen team is displayed in the notifications section.

Actual Result

Only the old team is displayed in the notifications section.

Event ID

No response

getsantry[bot] commented 4 months ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 4 months ago

Routing to @getsentry/product-owners-crons for triage ⏲️

davidenwang commented 4 months ago

Thanks @JeremiaAu for writing in about this. I was recently working on this component so I'll have a look and see if I can't correct this behavior

davidenwang commented 4 months ago

If you could also give me some info, which monitor are you trying to edit, and which team are you trying to replace the old team with?

JeremiaAu commented 4 months ago

Originally I only wanted to clear the team from the notification section since I was getting two separate mails for a missed checkin, but that also did not work. Last time I checked, the problem was present with all my existing cron monitors, and even new cron monitors I only created to confirm this bug. I am a member of both teams. I am also the superuser of the self hosted Sentry instance.

davidenwang commented 4 months ago

Originally I only wanted to clear the team from the notification section since I was getting two separate mails for a missed checkin, but that also did not work. Last time I checked, the problem was present with all my existing cron monitors, and even new cron monitors I only created to confirm this bug. I am a member of both teams. I am also the superuser of the self hosted Sentry instance.

Gotcha, I'll look more into this and reply back here