Redmine

Based on your description, the "Reporter" plugin's context menu export seems to be designed to operate on the currently displayed data, which is a common limitation of many web-based reporting tools. The fact that increasing the per-page limit partially helps confirms this behavior.

Here are a few potential avenues to explore, which may or may not be possible depending on the specific design and version of the Reporter plugin you are using:

1. Plugin Configuration and Documentation:

Check Plugin Settings: Re-examine the Reporter plugin's configuration options in Redmine's administration panel. There might be a setting you've overlooked that allows you to change the export scope from "current page" to "all results."

Consult Plugin Documentation: Search for the official documentation for the Reporter plugin. The developer might have addressed this specific issue or provided a solution for exporting all filtered records. A forum or GitHub repository for the plugin would also be a great place to ask this question directly to the developers or other users.

2. Alternative Export Methods within Redmine:

Redmine's Native Export: Before concluding that the Reporter plugin is the only way, check if Redmine's native Time Entries list has its own export functionality. Redmine often provides a CSV or PDF export option that can handle all filtered records, regardless of pagination. This is usually located at the bottom of the list or as a button near the filter options.

API Export: If you have some technical knowledge, Redmine's REST API is a powerful tool. You can use it to programmatically fetch time entries that match your filters and then generate your own report. This requires some scripting, but it's a guaranteed way to get all the data you need. You can find the API documentation on the Redmine website.

3. Customizing the Template (Advanced):

Modifying Plugin Files: This is an advanced and potentially risky option. If you have access to the Redmine server, you might be able to find and modify the Reporter plugin's files, specifically the template or the controller action responsible for the export. You would need to locate the code that fetches the records and change it to fetch all filtered records instead of just the paginated ones.

Caution: Modifying plugin files directly is generally not recommended. It can break the plugin, and your changes will be overwritten during a Redmine or plugin update. It's much better to look for a configuration option or an official solution.

4. A Practical Workaround:

Temporary Per-Page Increase: While not ideal, the simplest workaround is to temporarily set the per-page limit to a very high number (e.g., 9999) before performing the export. This will display all the records on a single page, allowing the Reporter plugin to export everything. Just remember to set it back to your desired value afterward https://www.paybyplatema.cx

Note: This may cause the page to load very slowly if you have a massive number of entries, and some servers might time out.

Given your specific use case, I would strongly recommend starting with checking the plugin's documentation and exploring Redmine's native export options. If those fail, the workaround of temporarily increasing the per-page limit is the most practical immediate solution. If you need a permanent fix and are comfortable with it, investigating the API is the most robust long-term solution.