-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Stage
-
Bug Type:Functional
-
Bug Severity:Medium
-
Level:Employee
-
Module:BenAdmin - Enrollment
-
Reported by:Client
-
Item State:Production Complete - Closed
-
Sprint:WT Sprint 30 -Bugs
Please refer to WT-9027 for background
Please see email from BCC below. I have also uploaded the screenshot. This issue is holding up their UAT for go live. Please look at this on priority.
Product: Universal Life Insurance
Rounding Rule: Set to Round up to next $1,000
This is the group that development had to allow for a .5 multiple of earnings to be allowed. We have the rule set at 1.5 X Earnings. It seems that the rounding works in the system for other scenarios we have built but NOT for the 1.5. Is it possible that when development allowed for the .5 multiple that they didn’t take that into consideration in their rounding logic.
Attached is an example of a person whose benefit should show as $146,000 based on how we have the plan built and the rounding rule, however, it is displaying as $145,750. .
Sumeet.Kolge (Inactive)
logged work - 01/Jun/17 11:42 AM -
- Time Spent:
- 3.3h
-
Analysis tried different scenarios for EE, discussion with jaideep.
Sumeet.Kolge (Inactive)
logged work - 02/Jun/17 05:12 AM -
- Time Spent:
- 2h
-
Analysis and cross-checked scenarios for random EEs.
-
- Time Spent:
- 6h
-
Analysis,discussion, coding,unit testing, code check in
-
- Time Spent:
- 4h
-
Scenario reproduced in local
code fix and unit testing with Shailendra
Call with Debbie and Satya
Query resolution for Debbie's comment
Discussion with Satya, Amruta, Prasad and Shailendra
Stage patch deployment follow up and smoke test in Stage
Shailendra Honrao (Inactive)
logged work - 05/Jun/17 12:41 PM -
- Time Spent:
- 4.5h
-
coding,unit testing,discussion
-
- Time Spent:
- 0.5h
-
Discussion with Satya, Jyoti and Shailendra
Shailendra Honrao (Inactive)
logged work - 06/Jun/17 05:30 AM -
- Time Spent:
- 1.5h
-
review,check in,unit testing
Sumeet.Kolge (Inactive)
logged work - 06/Jun/17 11:09 AM -
- Time Spent:
- 3.3h
-
Analysis , discussion with teams, tried different scenarios for different options under cost and coverage for rounding up.
-
- Time Spent:
- 0.5h
-
Code review and Unit Testing
Sumeet.Kolge (Inactive)
logged work - 07/Jun/17 12:30 PM -
- Time Spent:
- 1h
-
internal discussion with teams
Prasad Patil (Inactive)
logged work - 07/Jun/17 09:35 PM -
- Time Spent:
- 3h
-
analysis and Discussion with team.
Shailendra Honrao (Inactive)
logged work - 08/Jun/17 12:51 PM -
- Time Spent:
- 6h
-
reproducing issue,discussion with prasad,customization,code fix, unit test,review,code check in
Prasad Patil (Inactive)
logged work - 08/Jun/17 09:18 PM -
- Time Spent:
- 1h
-
Analysis and discussion with Shailendra.
Sumeet.Kolge (Inactive)
logged work - 09/Jun/17 10:13 AM -
- Time Spent:
- 3h
-
Created same scenario on LB long, tested this issue for all fields.
Prasad Patil (Inactive)
logged work - 09/Jun/17 06:16 PM -
- Time Spent:
- 2h
-
analysis and discussion with team.
-
- Time Spent:
- 0.25h
-
Discussion with Shailendra
Stage code commit
Prasad Patil (Inactive)
logged work - 12/Jun/17 07:04 PM -
- Time Spent:
- 2h
-
Analysis and discussion with Sumeet.
-
- Time Spent:
- 3.3h
-
analysis made scenarios of plan and contingency on production, tested this issue on production.
-
- Time Spent:
- 0.5h
-
Production code commit
Discussion with Jyoti for "Case 14 'Range Percentage of Monthly Salary"- Verified history of collection manage file in stage and production
- Case 14 is missing in production, so skipped related merge in production
Prasad Patil (Inactive)
logged work - 15/Jun/17 10:52 PM -
- Time Spent:
- 2h
-
Analysis and discussion with sumeet.
