...
Prioritization Items to Discuss
- Payroll Archive (Redesign Payroll CD
- USPS-R Canned Reports causing performance issues
- In USPS-R we have some canned reports that use and internal query process called a 'Chunk Provider' allowing them to process 100 records at a time before querying more data.
- This has become a problem as the Chunk Providers are leaking db connections.
- If all db connections are leaked, no users can login or preform any operations, forcing the ITC's to restart the app.
- This is the highest priority and every chunk provider should be refactored away in the next 2-4 releases of USPS-R
- Payroll Item Max Amounts
Jira Legacy server SSDT JIRA serverId 925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca key USPSR-4467)- Continues to be our top priority
- Payroll Init / Posting Bugs and Improvements
- Add a validate step to the Payroll Post process to report all errors before posting the payroll
- Add more context to history for Check / DD printing
- Lots of other minor improvements / bugs
- Compensation Pays Paid issue
- District paid contracts outside of the contract start / stop dates
- Moved start date so they could include the contract in a payroll
- Moved the start date back to 7/1/19 after payroll was completed
- This causes the pays paid calculation to be incorrect (based on the date range of the compensation)
- We have created a new feature to allow the pays paid to adjusted through compensation adjustments
- This issue will also change how we store the pays paid currently
- How soon after payroll archive should this be prioritized?
Jira Legacy server System JIRA serverId 6d21ed14-3f48-3cc2-ad28-6548879d10d6 key USPSR-4431
- District paid contracts outside of the contract start / stop dates
- Accrued wages are not displayed on Direct Deposit Notices / Check Stubs in certain situations
Jira Legacy server System JIRA serverId 6d21ed14-3f48-3cc2-ad28-6548879d10d6 key USPSR-4629 - Planned for 5.39.0 release, currently scheduled for 10/11/19
- Does it need to be moved up?
- Items from the floor?