Raise the default limit of log entries per page

[k-semenko]

Describe the problem

Currently, when viewing a failed Test Item in ReportPortal, the number of log entries per page is limited to 300. This makes it difficult to analyze long logs, especially when errors are preceded by a large amount of debug or contextual output. In many cases, the useful part of the log is beyond this 300-line window.

Manually clicking through pages is slow and disrupts the debugging flow.

Describe the solution you'd like

We'd like the ability to view more logs per page — ideally a configurable setting (or at least a higher upper limit). Setting the value manually in the URL query parameter (page.size=1000) does work, which suggests the limitation is enforced on the UI side.

💡 A default limit of 300 is too restrictive for real-world test logs. Allowing values like 600 or 1000 would significantly improve usability.

Steps to reproduce

1. Open a failed Test Item
2. Scroll through the logs
3. Only 300 log entries are visible per page
4. Manually editing the URL (e.g., page.size=1000) shows more logs — but this is not accessible through the interface

Suggested improvements

• Raise the default limit from 300 to a higher number (e.g., 600 or 1000)

Why this matters

Analyzing long logs is critical for understanding root causes of test failures. A hard-coded 300-line limit significantly limits visibility and slows down failure triage. This is especially painful in integration tests, performance scenarios, or multi-step flows with verbose logs.