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

ref(feedback): clean up search suggestion fields #87949

Merged
merged 3 commits into from
Apr 1, 2025

Conversation

aliu39
Copy link
Member

@aliu39 aliu39 commented Mar 25, 2025

contact_email
name
These are not valid search fields for /issues/. They were probably derived from the feedback context object. We have user.email and user.username instead

message
This is valid but you have to search for the whole msg, not a substring. Case and whitespace sensitive. IMO this is not a useful search, and suggestions are polluted by issue platform error messages and confusing:
Screenshot 2025-03-25 at 4 50 14 PM

transaction
This is a valid search for the transaction tag, however we don't include the tag in ingestion. So unless it's a custom tag attached by the sender, IMO we shouldn't suggest it. The suggestions for these are also from IP:
Screenshot 2025-03-26 at 10 50 29 AM

@aliu39 aliu39 requested a review from a team as a code owner March 25, 2025 23:51
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 25, 2025
@aliu39 aliu39 merged commit 461ca8f into master Apr 1, 2025
41 checks passed
@aliu39 aliu39 deleted the aliu/cleanup-feedback-search-fields branch April 1, 2025 20:00
andrewshie-sentry pushed a commit that referenced this pull request Apr 8, 2025
`contact_email`
`name`
These are not valid search fields for /issues/. They were probably
derived from the feedback context object. We have `user.email` and
`user.username` instead

`message`
This is valid but you have to search for the whole msg, not a substring.
Case and whitespace sensitive. IMO this is not a useful search, and
suggestions are polluted by issue platform error messages and confusing:
![Screenshot 2025-03-25 at 4 50
14 PM](https://github.com/user-attachments/assets/eb16c3e5-cdee-4291-82aa-3c9d8a5d4a45)

`transaction`
This is a valid search for the `transaction` tag, however we don't
include the tag in ingestion. So unless it's a custom tag attached by
the sender, IMO we shouldn't suggest it. The suggestions for these are
also from IP:
<img width="564" alt="Screenshot 2025-03-26 at 10 50 29 AM"
src="https://github.com/user-attachments/assets/fbfad771-179d-49a3-b9a8-a6065b4aa547"
/>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants