We would like to request improvements to the usability and performance of the “Completed Requests” list in the Registration Manager – Leave Requests module.
Current situation:In our school, we have accumulated over 16,000 completed leave request records. The Completed Requests list is ordered from the earliest start date to the most recent, with limited options to access recent records efficiently.
Current challenges:- To view the most recent completed requests, staff must click through more than 100 pages to reach the last page, which is time-consuming and inefficient.- Using “Show all” or setting page size to include all results often causes long loading times and pages failing to load due to the large volume of data.- There is no obvious way to sort by most recent date first, filter by a date range, or quickly narrow results to a relevant period.
Requested improvements:One or more of the following enhancements would significantly improve usability and performance:- Ability to sort Completed Requests by most recent date (descending order).- Filters for date ranges (e.g. last 7 days, last month, custom start/end dates).- Improved pagination or lazy loading for large datasets.- Optional archiving or hiding of older completed requests to reduce active dataset size.
Who would benefit:- Attendance staff and administrators who regularly review leave history.- Schools with medium to large student populations where leave request data grows quickly over time.- Users who need to audit, review, or report on recent leave activity efficiently.
Use case example:When reviewing recent absences or following up on attendance trends, staff are usually interested in requests completed within the last few days or weeks. Being forced to navigate hundreds of pages or load all records significantly affects productivity and system usability.
We believe these enhancements would improve both user experience and system performance, especially for schools with large datasets.
