-
Type:
Change Request
-
Status: Stage Testing
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Enrollment
-
Reported by:Support
-
Company:El Dorado
-
Item State:Stage QA - Production Deployment on Hold
-
Sprint:WT Sprint 37 - Enhancement, WT Sprint 38 - Enhancement
Vijay Siddha shyam sharmaUmesh Kadam Rakesh Roy
Hi Shyam,
During discussion Dave for El Dorado issues, a new customization request has been identified.
If employee make any changes from same date till enrollment period is going on then elections should not be terminated from end of month (or termination rule specified at company level). But within enrollment period his elections should be terminated one day prior to enrollment effective date rule.
We need to schedule this on high priority. Marking Dave also in Cc of this ticket. This links to El Dorado ticket WT-5646.
Cc: David Rhodes
Regards,
Satya Prakash
- causes
-
WT-11419 Election is not terminated as never effective after class change
-
- Rejected
-
-
-
- In Development
-
-
-
- Closed
-
- relates to
-
WT-1206 If additional field value has been changed then plan should not be allocated for 1 month
-
- Closed
-
-
WT-5646 [riskmanagement] WorkTerra confirmation
-
- Resolved
-
-
-
- Closed
-
-
- Time Spent:
- 1h
-
Design team meeting.
-
- Time Spent:
- 1h
- <No comment>
-
- Time Spent:
- 1h
-
Design team meeting for termination date rule and election termination assumption.
-
- Time Spent:
- 2h
-
Prepared analysis document
Discussion with Amruta
Reviewed analysis document from Amruta
-
- Time Spent:
- 0.25h
-
Discussion with Jaideep regarding Analysis document and terminate date assumptions.
-
- Time Spent:
- 0.25h
-
Discussion with Lalit regarding new assumption of termination date rule
-
- Time Spent:
- 1h
-
Discussion with Jyoti regarding implementation and its related tickets
Corrected analysis document and replied in JIRA comment
-
- Time Spent:
- 7h
-
Only for OE Approach :
Analysis
Discussion with Jyoti regarding code change areas and different approaches for code change, unit testing
-
- Time Spent:
- 7h
-
Only for OE Approach :
Analysis, Code debugging, code change
Discussion with Jyoti
Unit Testing for SP related changes and OE ongoing scenarios
-
- Time Spent:
- 4h
-
Code change, unit testing, impact testing
-
- Time Spent:
- 7.5h
-
Scenarios unit testing for code change suggested by Amruta
Design team meeting
Documentation
review with Amruta and Jyoti
Discussion with team
-
- Time Spent:
- 2h
- <No comment>
-
- Time Spent:
- 1h
-
Design Team meeting
Discussion with Amruta regarding scenario verification
-
- Time Spent:
- 5h
-
Client call
Scenario discussion and documentation
Preparation for demo
-
- Time Spent:
- 4.5h
-
Code change for EffectiveDate comparison
-
- Time Spent:
- 4h
-
Code change for EffectiveDate comparison
-
- Time Spent:
- 2h
-
Coding for EffectiveDate scenarios in core plan allocation with PageID (14,15)
-
- Time Spent:
- 2h
-
Coding for EffectiveDate scenarios in core plan allocation with PageID (14,15)
-
- Time Spent:
- 7h
-
Analysis and test case writing
-
- Time Spent:
- 8h
-
Coding for Page Level (Change Classes Screen and Change Status Screen) scenarios
-
- Time Spent:
- 5h
-
Coding for Page Level (Change Classes Screen and Change Status Screen) scenarios
-
- Time Spent:
- 5h
-
Coding for Page Level (Change Classes Screen and Change Status Screen) scenarios
-
- Time Spent:
- 3.5h
-
Discussion, Code Review and scenario discussion with Amruta
-
- Time Spent:
- 1h
-
Code review with Amruta and negative scenario discussion
-
- Time Spent:
- 4.5h
-
Code review with Amruta and negative scenario discussion, Unit Testing
-
- Time Spent:
- 1.5h
-
Unit testing for negative scenarios and LB code commit
-
- Time Spent:
- 8h
-
Test case execution on LB
-
- Time Spent:
- 8h
-
Test case execution on LB
-
- Time Spent:
- 6h
-
Scenario testing on Stage
-
- Time Spent:
- 1h
-
Scenario testing on Stage
