-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Bug Severity:Medium
-
Module:BenAdmin - Enrollment
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
Softchoice
JE DUNN
- plan level / company level termination date rule is set as end of current pay period (or anything like end of month)
- take an existing employee who is currently enrolled in above plans
- go on terminate plan election screen and put a termination date - save
- ideally plan termination date should set according to the termination date rule set at plan level if not then at company level
- here the termination date which you are putting is getting set as the final termination date for the plans
- when the same termination scenarios is tested with class change - plans got terminated according to the termination date rule set at plan level if not then at company level
CC - Prasad Pise Rakesh Roy Jyoti Mayne Amruta Lohiya Hrishikesh Deshpande Sachin Hingole
Note - on Stage - same issue exists
on LB - the termination date is not according to the plan as well as company level termination date rule
- relates to
-
WR-51 Selected termination date did not resets if corresponding benefit plan is deselected
-
- Closed
-
-
WT-2437 WT -> Election Termination Screens -> Show the calculated effective dates before user terminates any election
-
- Production Complete
-
-
WT-7125 Employbridge - Enhancement to Termination Date Rule
-
- Closed
-
-
WT-7637 Terminate Plan Elections screen showing dates like 1/1/1900 12:00:00 AM for all listed elections
-
- Production Complete
-
-
WT-8020 Termination date entered on Terminate Plan Elections gets cleared automatically
-
- Production Complete
-
Field | Original Value | New Value |
---|---|---|
Summary | Wt -> Terminate plan elections -> not terminating the plans according to the termination date rules set at plan / level | WT -> Terminate plan elections -> not terminating the plans according to the termination date rules set at plan / level |
Description |
Softchoice JE DUNN * plan level / company level termination date rule is set as end of current pay period (or anything like end of month) * take an existing employee who is currently enrolled in above plans * go on terminate plan election screen and put a termination date - save - ideally plan termination date should set according to the termination date rule set at plan level if not then at company level - here the termination date which you are putting is getting set as the final termination date for the plans - when the same termination scenarios is tested with class change - plans got terminated according to the termination date rule set at plan level if not then at company level CC - [~prasadp] [~rakeshr] [~jyoti.mayne] [~amruta.lohiya] [~hrishikesh.deshpande] [~sachin.hingole] |
Softchoice JE DUNN * plan level / company level termination date rule is set as end of current pay period (or anything like end of month) * take an existing employee who is currently enrolled in above plans * go on terminate plan election screen and put a termination date - save - ideally plan termination date should set according to the termination date rule set at plan level if not then at company level - here the termination date which you are putting is getting set as the final termination date for the plans - when the same termination scenarios is tested with class change - plans got terminated according to the termination date rule set at plan level if not then at company level CC - [~prasadp] [~rakeshr] [~jyoti.mayne] [~amruta.lohiya] [~hrishikesh.deshpande] [~sachin.hingole] Note - This works well on LB and Stage |
Description |
Softchoice JE DUNN * plan level / company level termination date rule is set as end of current pay period (or anything like end of month) * take an existing employee who is currently enrolled in above plans * go on terminate plan election screen and put a termination date - save - ideally plan termination date should set according to the termination date rule set at plan level if not then at company level - here the termination date which you are putting is getting set as the final termination date for the plans - when the same termination scenarios is tested with class change - plans got terminated according to the termination date rule set at plan level if not then at company level CC - [~prasadp] [~rakeshr] [~jyoti.mayne] [~amruta.lohiya] [~hrishikesh.deshpande] [~sachin.hingole] Note - This works well on LB and Stage |
Softchoice JE DUNN * plan level / company level termination date rule is set as end of current pay period (or anything like end of month) * take an existing employee who is currently enrolled in above plans * go on terminate plan election screen and put a termination date - save - ideally plan termination date should set according to the termination date rule set at plan level if not then at company level - here the termination date which you are putting is getting set as the final termination date for the plans - when the same termination scenarios is tested with class change - plans got terminated according to the termination date rule set at plan level if not then at company level CC - [~prasadp] [~rakeshr] [~jyoti.mayne] [~amruta.lohiya] [~hrishikesh.deshpande] [~sachin.hingole] Note - on Stage - same issue exists on LB - the termination date is not according to the plan as well as company level termination daet rule |
Description |
Softchoice JE DUNN * plan level / company level termination date rule is set as end of current pay period (or anything like end of month) * take an existing employee who is currently enrolled in above plans * go on terminate plan election screen and put a termination date - save - ideally plan termination date should set according to the termination date rule set at plan level if not then at company level - here the termination date which you are putting is getting set as the final termination date for the plans - when the same termination scenarios is tested with class change - plans got terminated according to the termination date rule set at plan level if not then at company level CC - [~prasadp] [~rakeshr] [~jyoti.mayne] [~amruta.lohiya] [~hrishikesh.deshpande] [~sachin.hingole] Note - on Stage - same issue exists on LB - the termination date is not according to the plan as well as company level termination daet rule |
Softchoice JE DUNN * plan level / company level termination date rule is set as end of current pay period (or anything like end of month) * take an existing employee who is currently enrolled in above plans * go on terminate plan election screen and put a termination date - save - ideally plan termination date should set according to the termination date rule set at plan level if not then at company level - here the termination date which you are putting is getting set as the final termination date for the plans - when the same termination scenarios is tested with class change - plans got terminated according to the termination date rule set at plan level if not then at company level CC - [~prasadp] [~rakeshr] [~jyoti.mayne] [~amruta.lohiya] [~hrishikesh.deshpande] [~sachin.hingole] Note - on Stage - same issue exists on LB - the termination date is not according to the plan as well as company level termination date rule |
Status | Open [ 1 ] | In Development [ 10007 ] |
Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) |
Developer | Umesh Kadam [ umesh.kadam ] | |
QA | Alankar Chavan [ alankar.chavan ] |
Remaining Estimate | 10h [ 36000 ] | 6h [ 21600 ] |
Time Spent | 4h [ 14400 ] | |
Worklog Id | 22691 [ 22691 ] |
-
- Time Spent:
- 4h
-
Analysis of an issue
Tried to reproduce an issue in LB, STAGE and Prodcution
Code commit verification
Discussion with Alankar, Rashmita, Jyoti, Satya and Rakesh for further action item
-
- Time Spent:
- 0.5h
-
Discussion with Umesh
Remaining Estimate | 6h [ 21600 ] | 5.5h [ 19800 ] |
Time Spent | 4h [ 14400 ] | 4.5h [ 16200 ] |
Worklog Id | 23309 [ 23309 ] |
Remaining Estimate | 5.5h [ 19800 ] | 5.25h [ 18900 ] |
Time Spent | 4.5h [ 16200 ] | 4.75h [ 17100 ] |
Worklog Id | 23615 [ 23615 ] |
Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) |
Item State | Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
Assignee | Umesh Kadam [ umesh.kadam ] | Alankar Chavan [ alankar.chavan ] |
Remaining Estimate | 5.25h [ 18900 ] | 4.75h [ 17100 ] |
Time Spent | 4.75h [ 17100 ] | 5.25h [ 18900 ] |
Worklog Id | 24525 [ 24525 ] |
Remaining Estimate | 4.75h [ 17100 ] | 4.5h [ 16200 ] |
Time Spent | 5.25h [ 18900 ] | 5.5h [ 19800 ] |
Worklog Id | 24527 [ 24527 ] |
Assignee | Alankar Chavan [ alankar.chavan ] | Jayshree Nagpure [ jayshree.nagpure ] |
Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
Item State | Parent values: LB QA(10201)Level 1 values: In Testing(10210) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
-
- Time Spent:
- 1h
-
testing termination issues and helping Jayshree
Remaining Estimate | 4.5h [ 16200 ] | 3.5h [ 12600 ] |
Time Spent | 5.5h [ 19800 ] | 6.5h [ 23400 ] |
Worklog Id | 24620 [ 24620 ] |
Item State | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) |
Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) |
Status | Local Testing [ 10200 ] | Stage Testing [ 10201 ] |
Item State | Parent values: Stage QA(10202)Level 1 values: In Testing(10214) | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) |
Assignee | Jayshree Nagpure [ jayshree.nagpure ] | Alankar Chavan [ alankar.chavan ] |
Item State | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) |
Status | Stage Testing [ 10201 ] | Production Testing [ 10202 ] |
Resolution | Unresolved [ 10200 ] | |
Status | Production Testing [ 10202 ] | Reopen in Production [ 10027 ] |
Status | Reopen in Production [ 10027 ] | In Development [ 10007 ] |
Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
Status | Local Testing [ 10200 ] | Stage Testing [ 10201 ] |
Status | Stage Testing [ 10201 ] | Production Testing [ 10202 ] |
Item State | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) | Parent values: Production Complete(10222)Level 1 values: Closed(10223) |
Resolution | Unresolved [ 10200 ] | Fixed [ 1 ] |
Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
Status | Production Complete [ 10028 ] | Closed [ 6 ] |
Remaining Estimate | 3.5h [ 12600 ] | 1.5h [ 5400 ] |
Time Spent | 6.5h [ 23400 ] | 8.5h [ 30600 ] |
Worklog Id | 25927 [ 25927 ] |
Bug Severity | Medium [ 16702 ] |
Environment_New | Production [ 18442 ] |
Transition | Time In Source Status | Execution Times |
---|
|
19h 47m | 1 |
|
3s | 1 |
|
3h 29m | 1 |
|
11d 3h 58m | 2 |
|
2d 3h 5m | 2 |
|
1d 19h 36m | 2 |
|
18s | 1 |
|
3s | 1 |
Hi Alankar Chavan,
As discussed, this issue is exists only in Production environment since
WT-2437is not yet deployed in Production.WT-2437will be deployed to Production once its related issues will get resolved.Thanks and Regards,
:: Umesh Kadam
CC : Satya, Rakesh Roy Jyoti Mayne, Harshawardhan Phalake, Rashmita Dudhe