-
Type:
Change Request
-
Status: Closed
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Platform
-
Labels:None
-
Module:Platform
-
Reported by:Support
-
Item State:Production Complete - Closed
-
Sprint:WT Sprint 36 - Enhancement
-
Severity:Simple
A time-out system (e.g. a screen saver) pauses the session screen after 15 minutes of inactivity, closes network sessions after 30 minutes of inactivity, and requires the user to reestablish authenticated access once the session has been paused or closed; or, if the system cannot be modified, a limited form of time-out that clears the screen but does not close down the application or network sessions is used.
-
- Time Spent:
- 3h
-
Analysis, Understanding business logic , code changes and unit testing.
-
- Time Spent:
- 0.25h
-
Explained Test scenario's to Sanjana
And test cases ofWT-9886
-
- Time Spent:
- 0.5h
-
Analysis
Internal discussion with jayshree about test cases
-
- Time Spent:
- 6h
-
Verified for SA, partner and broker
-
- Time Spent:
- 2.5h
-
Verified for broker,employee and default employee login
-
- Time Spent:
- 0.5h
-
Internal discussion with hrishikesh and sayali
Updating issue
-
- Time Spent:
- 10m
-
Creating surviving spouse credentials
-
- Time Spent:
- 4.5h
-
Verified on stage
Internal discussion
-
- Time Spent:
- 0.25h
-
UI Refresh branch check-in.
-
- Time Spent:
- 4h
-
Verified on azure using SA, Partner and broker login
Verified on production using partner login
Internal discussion with jayshree
-
- Time Spent:
- 4h
-
Verified on Azure and production for Web Application
Browser - Chrome,FirefoxVerified for below login :
1)Broker login
2)Employee login
3)Default login
4)Surviving spouse loginVerified session logout and continue pop-up message and also verified multiple login scenario.
-
- Time Spent:
- 1h
-
Testing
Internal discussion
updating jira