Hi Jmix team! 
First of all, thank you for the great work you’re doing on the platform — it keeps getting better and more powerful! 
I was wondering if pagination for the Quartz add-on (in job-model-list-view.xml) is something that might be considered for the roadmap. It would really help with scalability on the /quartz/jobmodels page, especially in environments where a large number of jobs have been executed and the list grows quite big.
Additionally, would it be possible to introduce a generic “retention” job implementation? The idea would be to periodically clean up configured “old” entities based on a SpEL condition (for example using creationDate or a similar field). This could potentially be applied to Quartz job models as well, even though they are not standard Jmix entities.
I think this could be a useful built-in mechanism for keeping datasets lean over time and reducing manual maintenance.
Thanks in advance for your feedback, and keep up the amazing work! 
Best regards,
Ale