casa
casa copied to clipboard
Allow Users to Save Column Display Preferences
What type(s) of user does this feature affect?
- supervisors
- admins
Description On the combined cases and volunteers page (see: https://github.com/rubyforgood/casa/issues/2694) we would like to make it possible for users to save their preferences regarding which columns to show and which to hide in the table.
Screenshots of current behavior, if any
The Current Select Displayed Columns Pop-up:
QA 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
password for all users: 12345678
When we say allow users to save preferences do we mean to the database? If so is there currently a pattern for this in the application or would that be entirely new behavior?
The other option would be saving the preferences to local storage in the browser.
When we say allow users to save preferences do we mean to the database? Yes
If so is there currently a pattern for this in the application or would that be entirely new behavior? New
Cool, I can take a swing at implementing this.
This issue has been inactive for 250 hours (10.42 days) and will be automatically unassigned after 110 more hours (4.58 days).
I am working on this now. Though the issue to implement the page this issue refers to https://github.com/rubyforgood/casa/issues/2694 has not been done yet. So right now I’m doing the model changes that will support the feature once that issue is done.
This issue has been inactive for 263 hours (10.96 days) and will be automatically unassigned after 97 more hours (4.04 days).
This issue has been inactive for 383 hours (15.96 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
I can work on this if still free to pick
@dpaola2 Is this a good issues to work on? @compwron can i work on this issue?
@dpaola2 Is this a good issues to work on? @compwron can i work on this issue?
@GALTdea, please go for it, if has some questions I can help since I started on it
Thanks @JuanVqz! I'll definitely hit you up if I run into something!
This issue has been inactive for 252 hours (10.50 days) and will be unassigned after 108 more hours (4.50 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 372 hours (15.50 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.
@GALTdea has been working hard on this, trying to figure out how to put it into In-Progress
This issue has been inactive for 251 hours (10.46 days) and will be unassigned after 109 more hours (4.54 days). If you have questions, please
If you are still working on this, comment here to tell the bot to give you more time
Still working on it!
This issue has been inactive for 240 hours (10.00 days) and will be unassigned after 120 more hours (5.00 days). If you have questions, please
If you are still working on this, comment here to tell the bot to give you more time
Need more time
Need more time
This issue has been inactive for 260 hours (10.83 days) and will be unassigned after 100 more hours (4.17 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 380 hours (15.83 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?
Completed in:
- PR1: https://github.com/rubyforgood/casa/pull/4769
- PR2: https://github.com/rubyforgood/casa/pull/4833
- PR3: https://github.com/rubyforgood/casa/pull/4840
!