Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

alerts:read Not a Valid Scope #82862

Closed
Kobby-Bawuah opened this issue Jan 3, 2025 · 4 comments
Closed

alerts:read Not a Valid Scope #82862

Kobby-Bawuah opened this issue Jan 3, 2025 · 4 comments
Labels
Product Area: Alerts Sync: Jira Apply to auto-create a Jira shadow ticket

Comments

@Kobby-Bawuah
Copy link

Kobby-Bawuah commented Jan 3, 2025

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

I have had at least two user reach out about a 400 error when attempting to set permissions for the Alerts field in a custom integration. The error response was:
The error reponse is "{"scopes":["alerts:read not a valid scope"]}"

Sample user case: https://sentry.zendesk.com/agent/tickets/141044

Steps to Reproduce:

  • Navigate to Custom Integrations > Edit Integration in Sentry.
  • Attempt to set the Alerts field to Read or Read & Write.
  • Observe the error response when saving changes.

Expected Result

The Alerts field should allow permissions such as Read or Read & Write without resulting in a 400 error.

Actual Result

Attempting to set permissions for the Alerts field results in the alerts: read not a valid scope error.

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

@getsantry
Copy link
Contributor

getsantry bot commented Jan 3, 2025

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Jan 3, 2025

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

@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 3 Jan 3, 2025
@mifu67
Copy link
Contributor

mifu67 commented Jan 6, 2025

Thanks for bringing this to our attention. We're working on a fix.

@mifu67
Copy link
Contributor

mifu67 commented Jan 8, 2025

The fix has been implemented. Let me know if the issue still persists.

@mifu67 mifu67 closed this as completed Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Product Area: Alerts Sync: Jira Apply to auto-create a Jira shadow ticket
Projects
Archived in project
Development

No branches or pull requests

2 participants