-
Type:
Change Request
-
Status: Closed
-
Priority:
Medium
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:
-
Module:BenAdmin - EDS
-
Reported by:Client
-
Item State:Stage QA - On Hold
-
Sprint:WT Sprint 36 - Enhancement, WT Sprint 38 - Enhancement
-
Severity:Simple
WORKTERRA will be auto generating the Payroll File No. the field that will have the auto generate set is "Payroll File No." on the Payroll page.
Can we set the auto generation on stage now this way we can test out the auto generation process? The client has given us the highest number, based on last weeks adds, so we can start with 035393. The Payroll File No. always has to be 6 digits long.
When the site moves up to production we can get the latest number from the client. We will mark the start number in the move to production ticket when the time comes.
-
- Time Spent:
- 20m
-
internal discussion with satya and vinayak
updated the comments
-
- Time Spent:
- 5.6h
-
Analysis and debugging of code.
Created new trigger to get the auto generated payroll file no for Employee_Payroll table.
-
- Time Spent:
- 0.5h
-
task explanation
scenario discussion
-
- Time Spent:
- 0.2h
-
Internal discussion with Rushikesh.
-
- Time Spent:
- 3h
-
Analysis - Code review
-
- Time Spent:
- 1h
-
Internal discussion with Satya and mailed regarding same to Rushikesh.
Check in done for LB and Trunk.
Updated comments.
-
- Time Spent:
- 3h
-
Analysis
Discussion with Sheetal
Test Cases Writing
-
- Time Spent:
- 0.5h
-
discussion with meghana
-
- Time Spent:
- 0.75h
-
Discussion with Meghana. Prepared Analysis document.
-
- Time Spent:
- 0.2h
-
Stage script check in
-
- Time Spent:
- 0.3h
-
Discussion with Swapnil.
Updated comments.
-
- Time Spent:
- 7h
-
Created new trigger which will update the payroll file no only when class3 changes are appears.
R&D on trigger with specific column change data.
Internal discussion with Swapnil.
-
- Time Spent:
- 4h
-
Modified the trigger and internal discussion with Swapnil.
-
- Time Spent:
- 0.2h
-
Updated analysis document.
-
- Time Spent:
- 2.5h
-
Analysis
Test Cases Writing
-
- Time Spent:
- 0.2h
-
Lb and Trunk check in.
-
- Time Spent:
- 2h
-
Discussion with Meghana on issue.
Discussion with swapnil.
Modified the stored procedure.
-
- Time Spent:
- 20m
-
Internal discussion with Jyotibala
-
- Time Spent:
- 2.5h
-
Internal discussion with Swapnil and Sheetal
Unit testing.
-
- Time Spent:
- 0.2h
-
Code review with sheetal
-
- Time Spent:
- 0.5h
-
Code review and scenario discussion
-
- Time Spent:
- 0.5h
-
Internal discussion with Meghana and Sudhir.
-
- Time Spent:
- 0.8h
-
Stage check in with the help of amit.
Internal discussion with Sheetal and Meghana.
-
- Time Spent:
- 1h
-
Discussion with Jyotibala and Meghana
verified Backend data on stage