-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Bug Fixed
-
Labels:None
-
Environment:Production
-
Categories:Enrollment - Credit Pool
-
Company:ATC
-
Reported by:White Label
We have two issues going on with the spending credits. Please see below, research and advise.
1. Brett Godey is not showing any spending credits for the vacation sell. HUB (Barbie Frizel) helped this person to enroll on 11/7/2017 and they have a confirmation statement showing the correct spending credits. When I look in the "view history" is looks like Barbie changed the vacation sell amount from 60 hours to -Select- but when I run a report with the form answer response and effective date is shows that the amount selected is 60 with the same time/date stamp. Can you please tell me why the credits are no longer showing.
2. Please run the election detail report below. The Spending Credits Allotted is not equaling the amount actually allotted. If I total the Spending Credits Applied and the Spending Credits Remaining I get the correct number. The number displayed in the system for Credits Allotted is correct
3. Is there a way to get the Total spending credits allotted/applied rather than showing on a report for each benefit? Can this be accomplished through an export maybe?
apxSpecs
-
- Time Spent:
- 6.5h
-
Issue analysis and data verification
Internal discussion with Prasanna and Amruta & JIRA update
-
- Time Spent:
- 0.75h
-
Discussion on Spending credits alloted, applied and remaining
Discussion regarding Spending cost coming zero for mentioned employee
-
- Time Spent:
- 5h
-
analysis, root cause finding, data scanning and correction, JIRA Update and Client call
-
- Time Spent:
- 4h
-
1) Checked template customization
2) Cost field implementation for column wise file
3) Analysis
4) Customization changes.
-
- Time Spent:
- 4.5h
-
discussion with Amruta, scenario creation given by amruta and client call
-
- Time Spent:
- 1.5h
-
correction on test company and JIRA Update
-
- Time Spent:
- 2h
-
reply to client queries, and data scanning
-
- Time Spent:
- 2h
-
- Analysis
- Jira Read
- Mail send for meeting
- check customization
-
- Time Spent:
- 6h
-
- Meeting With Amruta
- Discussion with Jyoti and umesh
- Initial Analysis,Check Customization , Issue Reproduce
- Document Creation
-
- Time Spent:
- 1h
-
scenario analysis meeting with amruta
-
- Time Spent:
- 2h
-
Discussion with team for solutions & issue understanding
-
- Time Spent:
- 6h
-
- Code Debug, Analysis, code fix analysis
- Unit testing
- company down to local script execution
-
- Time Spent:
- 1h
-
scenario verification and document review
-
- Time Spent:
- 8h
-
- Analysis
- Unit Test
- Code Debug
- Document Creation
- Discussion
-
- Time Spent:
- 8h
-
- Analysis
- Unit Test
- Code Debug
- Document Creation
- Discussion
-
- Time Spent:
- 0.5h
-
Discussion with Satya, Rohit and Rohan regarding documentation, different retro date scenarios
-
- Time Spent:
- 7h
-
- Scenario Creation, Unit Testing, Code Debug, Document Creation
-
- Time Spent:
- 4h
-
Analysis
Discussion with Rohan, Jyoti and Rohit for scenarios
-
- Time Spent:
- 1h
-
scenario explanation to Umesh and vijayendra
-
- Time Spent:
- 1.5h
- <No comment>
-
- Time Spent:
- 4h
-
Design Team Meeting
Scenario Discussion with Rohan and Jyoti
Documentation for Design Team Meeting
Scenario verification after Design Team Meeting
-
- Time Spent:
- 8h
-
Analysis for rate allocation behavior (action Item discussed in design team meeting)
Debugging and Analysis for Code changes
-
- Time Spent:
- 6.5h
-
Debugging and Analysis for code change
Discussion with Amruta for discrepancies in Rate allocation scenarios (Rates configured for two or more years)
Discussion with Rohan and Jyoti regarding discussed scenarios with discrepancies
-
- Time Spent:
- 6h
-
- Analysis and test case execution
-
- Time Spent:
- 7h
-
Approach : Loop through all records of credit pools allocated
Implementation and unit testing
-
- Time Spent:
- 6.5h
-
Approach : Max effective date of allocation credit pool
Implementation and Unit Testing
-
- Time Spent:
- 7h
-
Unit Testing
Impact testing
Discussion with Rashmita and Rohan
-
- Time Spent:
- 7h
-
Scenario and approach discussion with team
Code changes and Unit Testing
-
- Time Spent:
- 1.5h
-
Unit testing for scenarios discussed internally with enrollment team
-
- Time Spent:
- 3h
-
Design Team meeting
LB Code commit
-
- Time Spent:
- 0.5h
-
Discussion with Rohan and Jyoti
Shared MOM of design team meeting
-
- Time Spent:
- 0.25h
-
Production branch code commit
-
- Time Spent:
- 2h
-
- Issue testing on Production