We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
SaaS (https://sentry.io/)
Navigate to the issues page of the org mentioned in the shadow ticket
Observe the issues displayed without any filters applied. The issues load as expected.
Apply the following filter:
!error.type:HTTPException is:unresolved
When loading this URL, the page enters an infinite loading state and no issues are displayed.
The customer attempted to replicate the query using the API to debug further.
More information in this internal Jira ticket.
Issues
No response
The text was updated successfully, but these errors were encountered:
Auto-routing to @getsentry/product-owners-issues for triage ⏲️
Sorry, something went wrong.
I can verify that the UI hangs infinitely and that the endpoint call takes forever.
https://us.sentry.io/api/0/organizations/<foo>/issues/?collapse=stats&collapse=unhandled&environment=prod&expand=owners&expand=inbox&limit=25&project=<bar>&query=%21error.type%3AHTTPException%20is%3Aunresolved&savedSearch=0&shortIdLookup=1&statsPeriod=90d&utc=true
No branches or pull requests
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Navigate to the issues page of the org mentioned in the shadow ticket
Observe the issues displayed without any filters applied. The issues load as expected.
Apply the following filter:
When loading this URL, the page enters an infinite loading state and no issues are displayed.
The customer attempted to replicate the query using the API to debug further.
More information in this internal Jira ticket.
Expected Result
Actual Result
Product Area
Issues
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: