rubyforgood
Mobile View for Admin Dashboard
What type(s) of user does this feature affect?
- admins?
Description
The admin dashboard's table for monitoring supervisors' cases isn't responsive.
Make the data display cleanly on the screen for mobile devices.
Include screenshots in the pull request.
Screenshots of current behavior, if any
How to access the QA site
Login Details:
Link to QA site
Login Emails:
- [email protected] view site as a volunteer
- [email protected] view site as a supervisor
- [email protected] view site as an admin
- [email protected] view site as an all casa admin
- go to
/all_casa_admins/sign_in
- go to
password for all users: 12345678
Questions? Join Slack!
We highly recommend that you join us in slack #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.
It seems like the issue is related to lines 342, 352, and 363 in app/javascript/src/dashboard.js. There's dynamic padding that uses a multiplier (* 15) on the number of volunteers. This happens in three places: active contact, no contact, and transition-aged case. When those numbers get high, the padding grows too wide for small screens and causes the UI to overflow.
2 solutions come to mind:
- Make it a proportional calculation rather than a fixed one. In other words, if a supervisor has 10 volunteers, of which 7 are active, 2 are no contact, and 1 is transition-aged, then the green bar would take up 70% of the width, the red bar would take up 20%, and the blue bar would take up 10%.
- Make it a fixed width. In other words, regardless of the numbers, all 3 bars would take up a third of the width.
Assuming my understanding of the issue is correct, let me know which solution makes sense. Feel free to suggest alternative solutions or to let me know if I've not quite figured out the issue!
as I'm getting started on that solution (and focusing on this part of the app), I'm wondering if it also makes sense to visually separate the three metrics into two groups: (i) active contact vs no contact, and (ii) transition-aged youth.
I say this because the "active contact" and "no contact" metrics are mutually exclusive and clearly linked, whereas the "transition-aged youth" metrics seem to represent a different dimension, so grouping it with the other two doesn't feel intuitive. Perhaps I can bring it to the Friday meeting with stakeholders?
An example of what it could look like with the above in mind:
This issue has been inactive for 242 hours (10.08 days) and will be unassigned after 118 more hours (4.92 days). If you have questions, please
If you are still working on this, comment here to tell the bot to give you more time
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hey @compwron , just returning to this now! I joined the Friday meeting with stakeholders but there wasn't an admin around to answer my question about the potential design change. What's the best way to reach out to an admin to get their thoughts on this?
This issue has been inactive for 244 hours (10.17 days) and will be unassigned after 116 more hours (4.83 days). If you have questions, please
If you are still working on this, comment here to tell the bot to give you more time
This issue has been inactive for 247 hours (10.29 days) and will be unassigned after 113 more hours (4.71 days). If you have questions, please
If you are still working on this, comment here to tell the bot to give you more time
This issue has been inactive for 367 hours (15.29 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project.
This issue has been open without changes for a long time! What's up?