Bug 39450

Summary: OPAC ILL requests table should sort on ID desc by default
Product: Koha Reporter: Pedro Amorim <pedro.amorim>
Component: ILLAssignee: Pedro Amorim <pedro.amorim>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: pedro.amorim, tomascohen
Version: Main   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: Trivial patch Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: Bug 39450: Sort by ILL request ID DESC by default
Bug 39450: Sort by ILL request ID DESC by default

Description Pedro Amorim 2025-03-25 15:58:56 UTC
It's currently sorting on 'backend' DESC by default which in itself does not do a whole lot.
Comment 1 Pedro Amorim 2025-03-25 16:01:00 UTC
Created attachment 179687 [details] [review]
Bug 39450: Sort by ILL request ID DESC by default

To test:
1) Enable ILLModule
2) Create 2 ILL requests
3) Access the ILL table on the OPAC:
http://localhost:8080/cgi-bin/koha/opac-illrequests.pl
4) Notice the table is sorted on the 'Requested from' column.
5) Apply patch, repeat. Notice it's now showing the most recent requests first (sorting on ID DESC).

This is particularly important for Koha instances where patrons access this OPAC page often, and have multiple ILL backends installed
Comment 2 Brendan Gallagher 2025-04-02 08:05:32 UTC
Created attachment 180252 [details] [review]
Bug 39450: Sort by ILL request ID DESC by default

To test:
1) Enable ILLModule
2) Create 2 ILL requests
3) Access the ILL table on the OPAC:
http://localhost:8080/cgi-bin/koha/opac-illrequests.pl
4) Notice the table is sorted on the 'Requested from' column.
5) Apply patch, repeat. Notice it's now showing the most recent requests first (sorting on ID DESC).

This is particularly important for Koha instances where patrons access this OPAC page often, and have multiple ILL backends installed

Signed-off-by: Brendan Gallagher <brendan@bywatersolutions.com>
Comment 3 Pedro Amorim 2025-04-10 11:51:02 UTC
Making this duplicate of bug 39600 as the issue here is implicitly fixed by the work there.

*** This bug has been marked as a duplicate of bug 39600 ***