-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Bug Type:Functional
-
Bug Severity:Medium
-
Module:BenAdmin - Enrollment
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
-
Sprint:WT Sprint 31-Bugs
Customization :
- Company Level Rehire Effective Date Rule : Date 1st of the Month following XX (1) Month from Date of Rehire
- Company Level Effective Date Rule : Date of Change
- No new-hire / re-hire effective date rule on plan level
Steps to reproduce an issue :
- Add employee
- Core plans will be allocated as per new hire rules
- Change Employee's status to 'Terminated' from 'Change Status screen'
- Change Employee's status to 'Rehired' from 'Change Status screen'
- Core plans will not be allocated as per Rehire Effective Date Rule. Which is incorrect.
Expected result :
Core plans must be allocated as per eligible Rehire Effective Date Rule.
Example :
- If terminated employee's status is changed to Rehired with 06/23/2017 effective date.
- System will not consider Rehire Effective Date Rule and will allocate core plan(s) as per Company Level Effective Date Rule.
- Hence employee will get elections with 06/23/2017 effective date.
- relates to
-
WT-9743 LONG - Auto Enrolled Benefits - Rehires
-
- Resolved
-
Field | Original Value | New Value |
---|---|---|
Assignee | Vijay Siddha [ vijays ] | Jyoti Mayne [ jyoti.mayne ] |
Status | Open [ 1 ] | In Development [ 10007 ] |
Summary | *Rehire Effective Date Rule* set on company level is not getting considered while allocating core plan(s) to Rehired employees | "Rehire Effective Date Rule" set on company level is not getting considered while allocating core plan(s) to "Rehired" employees |
Dev Due Date | 29/Jun/2017 |
Description |
Customization : - Rehire Effective Date Rule : Date 1st of the Month following XX (1) Month from Date of Rehire - Company Level Effective Date Rule : Date of Change Steps to reproduce an issue : # Add employee # Core plans will be allocated as per new hire rules # Change Employee's status to 'Terminated' from 'Change Status screen' # Change Employee's status to 'Rehired' from 'Change Status screen' # Core plans will not be allocated as per Rehire Effective Date Rule. Which is incorrect. Expcted result : Core plans must be allocated as per eligibled Rehire Effective Date Rule. Example : - If terminated employee's status is changed to Rehired with 06/23/2017 effective date. - System will not consider Rehire Effective Date Rule and will allocate core plan(s) as per *Company Level Effective Date Rule*. - Hence employee will get elections with 06/23/2017 effective date. |
Customization : - Company Level Rehire Effective Date Rule : Date 1st of the Month following XX (1) Month from Date of Rehire - Company Level Effective Date Rule : Date of Change - No new-hire / re-hire effective date rule on plan level Steps to reproduce an issue : # Add employee # Core plans will be allocated as per new hire rules # Change Employee's status to 'Terminated' from 'Change Status screen' # Change Employee's status to 'Rehired' from 'Change Status screen' # Core plans will not be allocated as per Rehire Effective Date Rule. Which is incorrect. Expected result : Core plans must be allocated as per eligible Rehire Effective Date Rule. Example : - If terminated employee's status is changed to Rehired with 06/23/2017 effective date. - System will not consider Rehire Effective Date Rule and will allocate core plan(s) as per *Company Level Effective Date Rule*. - Hence employee will get elections with 06/23/2017 effective date. |
Assignee | Jyoti Mayne [ jyoti.mayne ] | Shailendra Honrao [ shailendra.honrao ] |
Remaining Estimate | 0h [ 0 ] | |
Time Spent | 0.5h [ 1800 ] | |
Worklog Id | 58746 [ 58746 ] |
-
- Time Spent:
- 5h
-
analysis,code debugging
Time Spent | 0.5h [ 1800 ] | 5.5h [ 19800 ] |
Worklog Id | 58828 [ 58828 ] |
-
- Time Spent:
- 0.5h
-
Scenario discussion with Shailendra
Item State | Parent values: Development(10200)Level 1 values: In Analysis(10204) | Parent values: Development(10200)Level 1 values: Ready for Review(10208) |
Item State | Parent values: Development(10200)Level 1 values: Ready for Review(10208) | Parent values: Development(10200)Level 1 values: Ready for Local Testing(10209) |
Code Review Date | 29/Jun/2017 | |
Code Reviewed By | Jyoti Mayne [ 11910 ] | |
Original Estimate | 0h [ 0 ] |
Attachment | WT_9927_Affected_Files.txt [ 53722 ] |
Attachment | Checklist_for_WT_9927.doc [ 53723 ] |
Assignee | Shailendra Honrao [ shailendra.honrao ] | Prasad Pise [ prasadp ] |
Developer | Shailendra Honrao [ shailendra.honrao ] |
Assignee | Prasad Pise [ prasadp ] | Alankar Chavan [ alankar.chavan ] |
Time Spent | 5.5h [ 19800 ] | 6.5h [ 23400 ] |
Worklog Id | 59279 [ 59279 ] |
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) |
Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: In Testing(10210) |
Time Spent | 6.5h [ 23400 ] | 7.5h [ 27000 ] |
Worklog Id | 59406 [ 59406 ] |
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:
- 6h
-
analysis,code debugging,discussion with umesh ,development,review by umesh and jyoti,impact testing,unit testing,code check in
Time Spent | 7.5h [ 27000 ] | 13.5h [ 48600 ] |
Worklog Id | 59418 [ 59418 ] |
Code Reviewed By | Jyoti Mayne [ 11910 ] | Jyoti Mayne,Umesh Kadam [ 11910, 15302 ] |
Time Spent | 13.5h [ 48600 ] | 14h [ 50400 ] |
Worklog Id | 59530 [ 59530 ] |
-
- Time Spent:
- 1h
-
Code debugging and Unit testing with Shailendra
Discussion with Shailendra and Jyoti
Production Due Date | 04/Jul/2017 | |
Stage Due Date | 3/Jul/17 [ 2017-07-03 ] |
Item State | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) |
Item State | Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) | Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) |
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: Ready for Production(10217) |
Status | Local Testing [ 10200 ] | Stage Testing [ 10201 ] |
Attachment | image001.jpg [ 53931 ] | |
Attachment | image002.png [ 53932 ] |
Attachment | image001.jpg [ 53933 ] | |
Attachment | image002.png [ 53934 ] |
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 | Fixed [ 1 ] | |
Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
Status | Production Complete [ 10028 ] | Closed [ 6 ] |
Item State | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) | Parent values: Production Complete(10222)Level 1 values: Closed(10223) |
-
- Time Spent:
- 3h
-
stage and production testing
Time Spent | 14h [ 50400 ] | 17h [ 61200 ] |
Worklog Id | 60527 [ 60527 ] |
Bug Severity | Medium [ 16702 ] |
Environment_New | Production [ 18442 ] |
Transition | Time In Source Status | Execution Times |
---|
|
14s | 1 |
|
5d 21h 8m | 1 |
|
3d 19h 17m | 1 |
|
4h 45m | 1 |
|
12s | 1 |
|
4s | 1 |
Please find 3Cs below :
Thanks and Regards,
Shailendra Honrao
CC : Satya,Jyoti Mayne,Umesh Kadam