-
Type:
Enhancement
-
Status: Production Complete
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Module:BenAdmin - Enrollment
-
Reported by:Support
-
Item State:Production Complete - Closed
-
Issue Importance:Must have Additional
-
Sprint:WT Sprint 23
This might be apply for screens like Terminate Election, terminate as never effective, terminate dependent's benefit
Here we want to notify an user - with which actual dates the elections are going to get terminated after he puts the termination dates.
Example - the termination rule is set as End of Month
User terminates an election with date 15th May 2016 - before the actual termination system should notify an user these changes are going to be effective from 31st May 2016
After this user can click on cancel or go further with the termination
This is as per the Dave's suggestion
- is blocked by
-
WT-8435 Server Error on Enroll now page
-
- Production Complete
-
- relates to
-
WT-7450 Terminate Dependent Benefit Screen => Known issue
-
- Production Complete
-
-
WR-51 Selected termination date did not resets if corresponding benefit plan is deselected
-
- 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
-
-
WT-8165 WT -> Terminate plan elections -> not terminating the plans according to the termination date rules set at plan / level
-
- Closed
-
-
WT-8487 Plan termination fail during termination of election
-
- Closed
-
-
- Time Spent:
- 0.5h
-
Design team meeting
-
- Time Spent:
- 6h
-
Analysis for the employee plan termination election
-
- Time Spent:
- 1h
-
design team meeting
-
- Time Spent:
- 1h
-
design team meeting and discussion with harsh
-
- Time Spent:
- 0.5h
-
Design team meeting
-
- Time Spent:
- 6h
-
coding and functionality review
-
- Time Spent:
- 3h
-
Code review and testing
-
- Time Spent:
- 3h
-
Code checkin and review and coding
-
- Time Spent:
- 1h
-
code change suggested in code review
-
- Time Spent:
- 3h
-
Code changes LB check-in and unit testing
-
- Time Spent:
- 0.5h
-
Analysis of this enhancement
-
- Time Spent:
- 1h
-
discussion and code checkin
-
- Time Spent:
- 3.5h
-
Analysis
Started Test Case Writting
-
- Time Spent:
- 1h
-
Task Analysis and team discussion for understanding.
-
- Time Spent:
- 1h
-
Team Discussion for task understanding
-
- Time Spent:
- 2.5h
-
test case writing
KT to Prasad and Jayshree
-
- Time Spent:
- 7.5h
-
Analysis and execution of test cases, Verification on LB.
-
- Time Spent:
- 2h
-
High level test execution and Queries discussion
-
- Time Spent:
- 0.5h
-
Updating of test cases and discussion with venkatesh
-
- Time Spent:
- 3.5h
-
Verification on stage.
-
- Time Spent:
- 0.5h
-
Discussion with Hrishikes
-
- Time Spent:
- 2h
-
script generation and analysis for issue
-
- Time Spent:
- 4.5h
-
Re-testing on Lb and issues discussion with alankar
-
- Time Spent:
- 1h
-
Debugged code for reported issue (LB re-opened)
Code correction done for reported issue
LB code commit
-
- Time Spent:
- 4h
-
Lb testing for remaining jira and then Stage testing after stage patch
-
- Time Spent:
- 0.5h
-
Stage patch code commit for this ticket and its dependent tickets
Smoke test
-
- Time Spent:
- 4.5h
-
Production testing
-
- Time Spent:
- 3h
-
Production code commit for
WT-2437and all its dependent (skipped UK changes while merging)
Smoke test after Production deployment
Resolved Production deployment error for moment.js
Smoke test after another Production deployment
Shared details with QA team for all its dependent tickets
-
- Time Spent:
- 1h
-
Video Preparing on Join me