-
Type:
Bug
-
Status: Production Complete
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: UI Refresh
-
Labels:None
-
Environment:Others
-
Bug Type:Functional
-
Bug Severity:Medium
-
Level:Employee
-
Module:BenAdmin - Enrollment
-
Reported by:CareerBuilder
-
Company:All Clients/Multiple Clients
-
Item State:Stage QA - Production Deployment on Hold
Environment: Azure
Company: FDU
Login: Employee
adhs06211986 Password@2 FDU
Credentials: Anderson Kia | 1457608 | Password@2 | FDU
Comments: For Confirmation Statement, this is the first time I am seeing Effective Date function. Can we reflect the selected effective date on both the PDF and Print version so if they are saving both, they can differentiate between the copies.
-
- Time Spent:
- 3h
-
--> Debugging and analysis.
--> Issue reproducing.
--> Discussion with Sachin.
-
- Time Spent:
- 2.5h
-
--> Code change for Effective date.
--> Unit testing .
--> Checkin done.
-
- Time Spent:
- 1h
-
verification discussion with Ramesh
-
- Time Spent:
- 1h
-
--> Discussion with Priya and Vijayendra.
-
- Time Spent:
- 3h
-
--> Issue reproducing on codemap with comparing to stage.
--> Issue reproducing on local.
--> not able to reproduce issue on local.
--> Comparing old effective date drop-down code with new code.
-
- Time Spent:
- 2h
-
--> Issue reproducing with NewHire and OE.
--> For OE workflow mode on codemap it was working fine.
-
- Time Spent:
- 1.5h
-
-->Was not reproducible issue , hence tested with Priya.
--> Following point tested with Priya
New hire and OE Mode On
New hire Mode > Confirmation Statement > 2 drop down appeared > Date 01012018 and 02012018
OE Mode > Confirmation Statement > 2 drop down appeared > Date 01012018 and 02012018
Through Menu 2 drop down > Confirmation Statement > 2 drop down appeared--> Discussed and assigned to Priya.