-
Notifications
You must be signed in to change notification settings - Fork 22
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
Autoselect bottom locations in location filter #1283
Comments
will resume after getting feedback from client in focus to see if we can wait until UI/UX person joins. |
@mahalakshme the message is changed as follows, will this do.?
|
|
|
@himeshr But my concern now is, it is inconsistent. The AC was to remove the message, since the working is same as in Search Filters and users are used to its working now. If we are adding message we need to add in both places. |
@mahalakshme MyDashboard already behaves the expected way. |
@1t5j0y can you please make the messaging consistent in both places - we can add the message in Search filters as well or remove it here. |
@Dinesh2019 separated custom report cards testing to different story. You can pair with whoever tests it, to be able to test such cards in future. |
- Introduce new translation key so users on older versions don't see incorrect help text
Added message to search and older filters view. |
@1t5j0y available for dev box |
Need:
As shown in the video, as part of UX, the expectation would be that on selecting a location, say State, all districts below it will be selected. And on unselecting a state, all districts below it will get unselected. Unselection currently is working for one level, but not selection. This is an issue because of below 2 reasons:
Acceptance criteria:
https://github.com/avniproject/avni-client/assets/10369963/7e49086d-0d84-44dd-9774-ab16a1d68874
-- Things to be noted in the above video:
Consider the below hierarchy:
-- 1. when a higher level location is selected say, a, automatically assume all the bottom locations(b,c,d,e,f,g) in the filter are selected though no need to show the selection in UI
-- 2. But when a particular location is selected(a and b) at a hierarchy level in the bottom, then only that location in that level is considered to be selected (a, b, d, e)
-- 3. Also when b is unselected, then all of b,c,d,e,f, and g needs to be considered selected.
The text was updated successfully, but these errors were encountered: