-
Type:
Bug
-
Status: Production Complete
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:
-
Environment:Stage
-
Bug Type:Functional
-
Bug Severity:Medium
-
Module:BenAdmin - Enrollment
-
Reported by:Implementation
-
Company:Bio-Rad
-
Stage Company Name:BioRad
-
Item State:Production Complete - Closed
-
Sprint:WT Sprint 41, WT- Sprint 42
In Stage for site BioRad we have a health tier built "Family" this tier is set in the EAP plan design for the Auto Enroll tier. When a new dependent is added in the New Hire window the EAP updates automatially HOWEVER when a dependent is added during a QE the EAP does not update. NH elections don't pend for HR approval and QEs do pend for HR Approval. I thought maybe it was the pending on the QEs but when I tested using the Admin event, which does not pend, the EAP auto enroll didn't add my new dependent automatically.
Please review this bug and provide feedback.
cc;Amit ThorveYamilka CocaRobyn Adkisonpeggy fiedlerGary Cunningham
-
- Time Spent:
- 8h
-
take back up of the company
restore it on local
executing scripts
analysis of issue
creating scenarios to test an issue
share finding with umesh and venkatesh
draft comment and get it reviewed by umesh kadam
-
- Time Spent:
- 0.5h
-
Discussion with Shailendra
-
- Time Spent:
- 3.5h
-
analysis, scenario verification and reply to client query
-
- Time Spent:
- 0.5h
-
comment review and scenario discussion
-
- Time Spent:
- 8h
-
Issue Analysis.
Discussion with jyoti and Shailendra.
Data analysis.
Issue reproduce.
Discussion with jyoti regarding domain knowledge.
Tried scenarios.
Comment on jira.
-
- Time Spent:
- 0.5h
-
scenario discussion with Amruta and code debug
-
- Time Spent:
- 5.5h
-
Discussion with Amruta
Code changes for adding child in core plans with retro/in between effective dates
Unit Testing
-
- Time Spent:
- 6.5h
-
Discussion with Amruta
Code changes for adding child in core plans with retro/in between effective dates
Unit Testing
-
- Time Spent:
- 5h
-
Discussion with Amruta
Code changes for adding child in core plans with retro/in between effective dates
Code changes for adding child in core plans with future effective dates (OK/Cancel popup scenarios for core plan allocation)
Unit Testing
-
- Time Spent:
- 8h
-
Discussion with Amruta
Code changes for adding child in core plans with retro/in between effective dates
Code changes for adding child in core plans with future effective dates (OK/Cancel popup scenarios for core plan allocation)
Unit Testing, Integration testing
-
- Time Spent:
- 4h
-
Code review and integration testing with Amruta
Deployment discussion with Gaurav and Amruta
-
- Time Spent:
- 0.5h
-
Follow up for code commit of dependent JIRAs
Discussion with Satya, Jyoti and Shailendra
Production code commit