-
Notifications
You must be signed in to change notification settings - Fork 152
Open
Description
Description
The Team Unassigned Build Errors table lacks the sorting and pagination functionality that is present on other error log tables on the same page. This inconsistency makes it difficult to navigate, manage, and prioritize unassigned errors, especially when the list grows long.
The sorting button implements sorting via URL query parameters (e.g., ?sort=build_count desc), but these parameters have no effect on the Team Unassigned Error Logs table.
Steps to Reproduce
- Log in as a user who is part of a team.
- Navigate to https://runbot.odoo.com/runbot/errors?sort=build_count%20desc
- Observe the two tables
Expected Behavior
The `Team Unassigned Error Logs` table should have feature parity with the main error log table:
- Pagination controls should be displayed at the bottom of the table to allow navigation through multiple pages of results.
- The table's content should respect the sorting parameters present in the URL.
Actual Behavior
The `Team Unassigned Error Logs` table is static. It does not provide any controls for sorting or pagination, and it does not respond to URL sorting parameters.Metadata
Metadata
Assignees
Labels
No labels