casa icon indicating copy to clipboard operation
casa copied to clipboard

Allow Users to Save Column Display Preferences

Open CovenantHuman opened this issue 3 years ago • 7 comments

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: Select Columns Popup

QA Login Details:
Link to QA site

Login Emails:

password for all users: 12345678

CovenantHuman avatar Oct 05 '21 02:10 CovenantHuman

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.

ludamillion avatar Oct 13 '21 13:10 ludamillion

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

compwron avatar Oct 13 '21 19:10 compwron

Cool, I can take a swing at implementing this.

ludamillion avatar Oct 14 '21 04:10 ludamillion

This issue has been inactive for 250 hours (10.42 days) and will be automatically unassigned after 110 more hours (4.58 days).

github-actions[bot] avatar Oct 25 '21 00:10 github-actions[bot]

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.

ludamillion avatar Oct 25 '21 00:10 ludamillion

This issue has been inactive for 263 hours (10.96 days) and will be automatically unassigned after 97 more hours (4.04 days).

github-actions[bot] avatar Nov 05 '21 00:11 github-actions[bot]

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.

github-actions[bot] avatar Nov 10 '21 00:11 github-actions[bot]

I can work on this if still free to pick

JuanVqz avatar Oct 19 '22 13:10 JuanVqz

@dpaola2 Is this a good issues to work on? @compwron can i work on this issue?

GALTdea avatar Mar 06 '23 17:03 GALTdea

@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

JuanVqz avatar Mar 06 '23 18:03 JuanVqz

Thanks @JuanVqz! I'll definitely hit you up if I run into something!

GALTdea avatar Mar 06 '23 18:03 GALTdea

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

github-actions[bot] avatar Mar 25 '23 00:03 github-actions[bot]

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.

github-actions[bot] avatar Mar 30 '23 00:03 github-actions[bot]

@GALTdea has been working hard on this, trying to figure out how to put it into In-Progress

dpaola2 avatar Mar 30 '23 13:03 dpaola2

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

github-actions[bot] avatar Apr 10 '23 00:04 github-actions[bot]

Still working on it!

GALTdea avatar Apr 10 '23 00:04 GALTdea

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

github-actions[bot] avatar Apr 20 '23 00:04 github-actions[bot]

Need more time

GALTdea avatar Apr 20 '23 03:04 GALTdea

Need more time

GALTdea avatar Apr 20 '23 04:04 GALTdea

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

github-actions[bot] avatar May 01 '23 00:05 github-actions[bot]

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.

github-actions[bot] avatar May 06 '23 00:05 github-actions[bot]

This issue has been open without changes for a long time! What's up?

github-actions[bot] avatar Jul 05 '23 02:07 github-actions[bot]

Completed in:

  1. PR1: https://github.com/rubyforgood/casa/pull/4769
  2. PR2: https://github.com/rubyforgood/casa/pull/4833
  3. PR3: https://github.com/rubyforgood/casa/pull/4840

!

littleforest avatar Jul 28 '23 18:07 littleforest