You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a brief flash of the login page on refresh of the ui. This can be quite noticeable when the page has been idle for some time.
The filtering currently only filters what's been returned from the /search (i.e. current table results) and not reachable to search beyond that scope. Expected UX:
a. If a user sets some filter, say Group Name, and then clicks SEARCH, this should return any entities with the user's set group name. This is possible by modifying the elastic search query to include filters.
As with filtering, same goes for column sorting. It only sorts the results from /search
User needs to click SEARCH to query beyond the scope of current result. Ideally, the user should be informed of this behavior
Filter operators from the MUI's DataGrid component that are not being handled by the application should ideally be removed
Clicking the CLEAR button returns No record found message, this should ideally return the default results.
The query parameters (in the browser url field) aren't being handled by the application, but are being set in the url every time a user filters their search
@libpitt Thanks for the list and we'll prioritize and make plans accordingly. @BirdMachine just a heads-up, no immediate actions needed as we are still finishing the documentation work.
/search
(i.e. current table results) and not reachable to search beyond that scope. Expected UX:a. If a user sets some filter, say Group Name, and then clicks SEARCH, this should return any entities with the user's set group name. This is possible by modifying the elastic search query to include filters.
/search
No record found
message, this should ideally return the default results.The attached video addresses some of these issues.
https://github.com/user-attachments/assets/a663273b-2821-42a3-92f1-b9792e74ff59
The text was updated successfully, but these errors were encountered: