-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Search by lack of Jira issue #8338
Comments
cc @macqueen |
Closing this issue due to staleness. Feel free to comment here if you think we should still work on this. |
Yes, I still think this would be a good feature to help me triage the exceptions that haven't been triaged yet. |
@pupeno asking around in our dedicated search and storage team and will respond here if this is something that can be done fairly easily or not. |
Thank you :) |
Turns out this is non-trivial as I suspected but we have a larger project going on that may make it easier in the future. That future is no sooner than 2021 though. Will reopen as I've seen a few more similar requests but do not expect progress soon. |
- "linked" means there is an issue linked to the group. - "unlinked" means there isn't an issue linked to the group. The implementation mirrors that of the `is:assigned`/`is:unassigned` filters where it does a non-snuba, postgres filter for `Group`s that are either linked to: - an `ExternalIssue` (via `GroupLink` with `LinkedType.issue`), or - a `PlatformExternalIssue` Fixes getsentry#15725, fixes getsentry#8338, fixes getsentry#5413, fixes getsentry#15525.
…21593) - "linked" means there is an issue linked to the group. - "unlinked" means there isn't an issue linked to the group. The implementation mirrors that of the `is:assigned`/`is:unassigned` filters where it does a non-snuba, postgres filter for `Group`s that are either linked to: - an `ExternalIssue` (via `GroupLink` with `LinkedType.issue`), or - a `PlatformExternalIssue` Fixes #15725, fixes #8338, fixes #5413, fixes #15525.
I'm guessing this applies to all external issue trackers, not Jira. My triaging process is creating an issue connected to the Sentry exception (or finding and connecting to an existing one), so, it would be good to have a way to find those without any assigned yet. Those would be the issues that need triaging for me.
The text was updated successfully, but these errors were encountered: