Project

General

Profile

Actions

roos-fs tasks #564

open

Add Session Expiry Warning and Renewal Mechanism to Prevent Data Loss

Added by Vadim Pariev 7 months ago. Updated 5 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
10/17/2025
Due date:
% Done:

0%

Estimated time:

Description

A user reported that their session expired while they were actively working in the application. Specifically, while creating a new task template, they spent over 30 minutes discussing and making changes before attempting to save. Unfortunately, their session had expired, causing all progress to be lost.

The current behavior leads to user frustration and potential data loss when work is performed over longer periods of inactivity, even if the user is actively interacting with the interface.

Expected Behavior:

When a user’s session is about to expire, the system should proactively notify them and give an option to extend the session. This ensures that their current work can be saved without requiring a re-login.

Proposed Solution / Business Logic:

Session Expiry Warning:

When the session is about to expire (e.g., 1 minute before timeout), display a modal notification or banner with a countdown.

Example text:

“Your session will expire in 1 minute. Would you like to stay logged in?”

User Options:

  • Proceed / Stay Logged In:

When clicked, the system sends a request to renew the session token and resets the session timer.

  • No Action:

If the user does not respond before the countdown ends, the session expires as usual, and they are logged out.

Post-Expiration Handling:

If the user’s session expires, show a clear message:

“Your session has expired. Please log in again to continue.”

Acceptance Criteria:

  • The system displays a session-expiry warning 1 minute before timeout.
  • Clicking “Stay Logged In” renews the session and continues seamlessly.
  • If the user takes no action, the session expires normally, and the user is logged out.
  • The user is informed when the session actually expires.
  • This feature works across application
Actions #1

Updated by Vadim Pariev 7 months ago

  • Description updated (diff)
Actions #2

Updated by Vadim Pariev 7 months ago

  • Status changed from Backlog to Open
  • Assignee set to Vadim Pariev
Actions #3

Updated by Vadim Pariev 7 months ago

  • Assignee changed from Vadim Pariev to Ivan Danyliv
Actions #4

Updated by Ivan Danyliv 6 months ago

  • Status changed from Open to In progress
Actions #5

Updated by Ivan Danyliv 6 months ago

  • Status changed from In progress to In review
Actions #6

Updated by Anton Obolientsev 6 months ago

  • Status changed from In review to Deployed (QA)
Actions #7

Updated by Olena Tretjakova 6 months ago

  • Status changed from Deployed (QA) to Ready for Deployment (prod)

** Environment: Staging.**

** Expected Result:**
After 29 minutes of inactivity on the site, the message "Your session will expire soon" appears with two buttons: "Stay logged in" and "Logout". Unless the user clicks "Stay logged in", they will be logged out.

** Steps ro Reproduce:**

  1. Log in and wait for 29 minutes.
  2. After 29 minutes of inactivity, a message appears saying the session will expire, and the user will be logged out unless they click 'Stay logged in'.

** Attachment:**
https://screenrec.com/share/rdXhKzlxLU

Actions #8

Updated by Vadim Pariev 6 months ago

  • Status changed from Ready for Deployment (prod) to Closed
Actions #9

Updated by Vadim Pariev 2 months ago

  • Assignee changed from Ivan Danyliv to Vadim Pariev
Actions #10

Updated by Albert Katasonov 5 days ago

  • Project changed from 8 to Roos-fs-ZIP
Actions

Also available in: Atom PDF