-
Type:
Bug
-
Status: In Development
-
Priority:
High
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Stage, QA
-
Bug Type:Functional
-
Bug Severity:Medium
-
Level:Admin, Candidate, Employee, Partner
-
Module:BenAdmin - Customization
-
Reported by:Harbinger
-
Company:All Clients/Multiple Clients
-
Item State:Development - On Hold
-
Issue Importance:Q2
Date picked after 31 Dec 2020 is automatically getting populated with year of previous century i.e. 19XX.
Replication Steps:
1. Login as SA/Partner/Employee
2. Go to test company like
'UiRefresh Test QA2' on Azure
OR
"ACAAutomation" on Stage
3. Go to Add Employee or Any form which has Date Picker.
4. Click on Date Picker.
4. Select a Date from Date picker like 28 May 2023. (Do No Type Anything)
5. After Date selection click any where else in the screen.
6. Check for the Date populated in Date field.
Expected Result:
Date should be populated which ever is selected.
Actual Result:
Date selected after 31 Dec 2020 is automatically getting populated with year of previous century i.e. 19XX.
PFA Screenshots
CC : Rakesh RoySachin HingoleHrishikesh DeshpandeVijayendra ShindeRohan J KhandaveSatya
This issue exist throughout the Workterra application on all environments along with new UI too. Also, as observed this issue can be with Date format mm/dd/yy
Hi Satya,
This is due to UK benefits changes.Can you please assign it to respective team member?
Thanks,
Sheetal Bodhale
Sheetal Bodhale (Inactive)
added a comment - Hi Satya ,
This is due to UK benefits changes.Can you please assign it to respective team member?
Thanks,
Sheetal Bodhale Whenever you select year after 2020,In WORKTERRAShared.js file values are hard coded.so though you select 20 it appends century as 19.Did some changes,after that upto year 2049 its working fine but when you select year as 2050 again it appends 19 as century(1950).
Please look in to the issue.
Punam Satpute (Inactive)
added a comment - Whenever you select year after 2020,In WORKTERRAShared.js file values are hard coded.so though you select 20 it appends century as 19.Did some changes,after that upto year 2049 its working fine but when you select year as 2050 again it appends 19 as century(1950).
Please look in to the issue. Hi Prasad Pise,
Please find below 3C's of the issue,
Concern: Date picked after 31 Dec 2020 is automatically getting populated with year of previous century i.e. 19XX.
Cause: Whenever you select year after 2020,In WORKTERRAShared.js file values are hard coded.
Correction:Script changes
Scenarios:
Previous Working: When you select date in date picker with year as '2020' or above '2020' then it was taking year as '1920', which is incorrect.
Current Working: Solved this problem. Now whenever you select date with year '2020' or '1920' or whichever, it will display the correct date with correct year.
Kindly check this in entire project. As discussed with Satya this exists in entire project.
Note: Punam Satpute please mention your changes against date picker issue.
Thanks,
Akshay Mukkawar
-------------------------------
CC:Sheetal Bodhale,Satya,Punam Satpute
Akshay Mukkawar (Inactive)
added a comment - - edited Hi Prasad Pise ,
Please find below 3C's of the issue,
Concern: Date picked after 31 Dec 2020 is automatically getting populated with year of previous century i.e. 19XX.
Cause: Whenever you select year after 2020,In WORKTERRAShared.js file values are hard coded.
Correction:Script changes
Scenarios:
Previous Working: When you select date in date picker with year as '2020' or above '2020' then it was taking year as '1920', which is incorrect.
Current Working: Solved this problem. Now whenever you select date with year '2020' or '1920' or whichever, it will display the correct date with correct year.
Kindly check this in entire project. As discussed with Satya this exists in entire project.
Note: Punam Satpute please mention your changes against date picker issue.
Thanks,
Akshay Mukkawar
-------------------------------
CC: Sheetal Bodhale , Satya , Punam Satpute Prasad Pise: Please make sure this is getting verified throughout the system as it's common function getting used across system.
Regards,
Satya Prakash
Cc: Rakesh Roy Akshay Mukkawar Sheetal Bodhale Samir Vijay Siddha
Refer attached test cases
Thanks,
Sanjana Jadhav.
CC: Rakesh Roy Prasad Pise Hrishikesh Deshpande Sachin Hingole Jayshree Nagpure
Verified on LB.
Verified using SA, Admin and employee login on Benadmin and onboard module
Please refer attached checklist:
scanerios.ods
Thanks,
Sanjana Jadhav.
CC: Rakesh Roy Hrishikesh Deshpande Prasad Pise Sachin Hingole
Due to some open issues, assigning this jira back to you. Once it's get resolved assigned back to me.
Thanks,
Sanjana Jadhav.
This is kept on hold due to dependent issue fixes. QA will verify the fixes and mark this bug as ready for stage.
Hi Sanjana Jadhav,
This issue is dependent UK benefits.please assign it to respective team member.
Thanks,
Akshay Mukkawar
----------------------------
CC:Sheetal Bodhale,Satya,Swapnil Pandhare,Prasad Pise
Akshay Mukkawar (Inactive)
added a comment - Hi Sanjana Jadhav ,
This issue is dependent UK benefits.please assign it to respective team member.
Thanks,
Akshay Mukkawar
----------------------------
CC: Sheetal Bodhale , Satya , Swapnil Pandhare , Prasad Pise This issue is related to UK benefits. Hence assigning this jira back to you.
Once it's get resolved assigned back to me.
CC: Rakesh Roy Hrishikesh Deshpande Prasad Pise Sachin Hingole
Thanks,
Sanjana Jadhav.
Cc: Sheetal Bodhale