rubyforgood
Create A Timeout Warning Before Users Are Automatically Logged Off
What type(s) of user does this feature affect?
- volunteers
- supervisors
- admins
Description Currently when a user leaves a window open without activity for an extended period of time there is no indication telling the user that they have been logged off behind the scenes until they refresh the page. This leads to users losing data when they try to save data on a page that they're actually logged out of. We would like a pop up that warns users when they are about to be automatically logged out two minutes before it happens. Ideally this pop-up would say something like "Warning: You are going to be logged out due to inactivity in two minutes. Please save or make a copy of your work now, to avoid loss.".
Screenshots of current behavior, if any
Before a Refresh:
After A Refresh:
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
In general please only claim one issue at once and pick up the next one when you finish the previous one. :)
No problem! 🙂
On Fri, Oct 8, 2021, 21:00 compwron @.***> wrote:
In general please only claim one issue at once and pick up the next one when you finish the previous one. :)
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/rubyforgood/casa/issues/2437#issuecomment-939053694, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI7XCXQCHQJG46HSRW5RQRTUF45WDANCNFSM5CPAFM4A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
This issue has been inactive for 262 hours (10.92 days) and will be automatically unassigned after 98 more hours (4.08 days).
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been inactive for 382 hours (15.92 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
No, I am sorry, I am not.
On Thu, Nov 4, 2021, 01:08 github-actions[bot] @.***> wrote:
This issue has been inactive for 382 hours (15.92 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rubyforgood/casa/issues/2437#issuecomment-960309025, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI7XCXQAJNKYSPIKUAFOPMLUKHFIRANCNFSM5CPAFM4A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
This issue has been inactive for 485 hours (20.21 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
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.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 inactive for 601 hours (25.04 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 inactive for 601 hours (25.04 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 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