-
Notifications
You must be signed in to change notification settings - Fork 915
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
Provide feedback on an entity is difficult when you have a big DB #6113
Comments
We have a delay (1.5 seconds, which seems a bit long I think) on some inputs (CreatedBy, Assignees, Status), but not on this field used here for searching entities. Should we add this delay ? @nino-filigran |
If the delay works then we could try it it, yes. We just need to ensure that when the searched is triggered, the app does not become so "buggy", and the delay seems to be a good solution to me. |
We just need the "palette" for entity type scoping in the search field. |
And also override the results instead of cumulating. |
Description
When trying to provide feedback and selecting the entity to provide feedback for trhough the user profile, feedback, if the DB is full with a lot of information, it is basically impossible to find the entity
Environment
Testing and demo
Reproducible Steps
Steps to create the smallest reproducible scenario:
Expected Output
Ability to find my query
Actual Output
The words are not added at the same rythm I type
The research does not found my result and eventually close itself
In theory, if we keep the same beahvior, either we should be able to filter on the type of entity maybe or trigger the search manually or simply ensure that the search is sent X seconds after the users stops to add inputs?
Additional information
Screenshots (optional)
Recording.bug.feedback.mp4
The text was updated successfully, but these errors were encountered: