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

Support for tags, aggregate data in Issues dataset for Dashboard widgets #60840

Closed
rpropst opened this issue Nov 29, 2023 · 4 comments
Closed

Comments

@rpropst
Copy link

rpropst commented Nov 29, 2023

Problem Statement

The issues dataset is the only way users can get to issue state, but using it prevents including columns such as count() (aggregation) or event values like tags.

Additionally it doesn't support filtering on these values

This makes it impossible to create a widget we need such as:

  • Show a widget of all issues where count_unique(user) is > 1000
  • Show a widget of issues with the associated custom tag value (such as feature flag)

Solution Brainstorm

No response

Product Area

Dashboards

@getsantry
Copy link
Contributor

getsantry bot commented Nov 29, 2023

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Nov 30, 2023

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

@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 Nov 30, 2023
@nanoburd
Copy link

nanoburd commented Dec 5, 2023

Do we think this is necessary for dashboards or perhaps is a more general way to "prioritize" and filter issues in the issue feed?

cc/ @rachrwang

@alexjillard
Copy link
Member

As progress is made on EAP and the Issues data is exposed, features like this should become possible. @phacops feel free to reopen if isn't the case.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

4 participants