Bug 29972 - The "select a specific item" table on opac-reserve.tt should be column configurable
Summary: The "select a specific item" table on opac-reserve.tt should be column config...
Status: RESOLVED DUPLICATE of bug 29713
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Lucas Gass (lukeg)
QA Contact: Testopia
URL:
Keywords:
Depends on: 29899
Blocks:
  Show dependency tree / graph
 
Reported: 2022-01-28 21:09 UTC by Lucas Gass (lukeg)
Modified: 2022-01-31 14:39 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: Small patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Bug 29972: Make the select a specific item table configurable on opac-reserve.tt (8.06 KB, patch)
2022-01-28 22:10 UTC, Lucas Gass (lukeg) 		Details | Diff | Splinter Review
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Gass (lukeg) 2022-01-28 21:09:22 UTC 
When you select a specific item on opac-reserve.tt there is a table which is not cannot be configured via Table settings, it would be nice if it could be.
Comment 1 Lucas Gass (lukeg) 2022-01-28 22:10:31 UTC 
Created attachment 129960 [details] [review]
Bug 29972: Make the select a specific item table configurable on opac-reserve.tt

To test:
1. Apply patch and restart everything
2. Find a record that was multiple items on it, place a hold on that item.
3. On the "Placing hold" page, click "Show more options" and "A specific
  item."
4. See that the table can now be sorted by each column, make sure the sorting works
5. Go to Administration > Table settings, and in the OPAC section find reserves_table
6. Try hiding some columns and then do step 3 again.
7. Confirm the columns are properly being hidden.
Comment 2 Katrin Fischer 2022-01-29 22:43:50 UTC 
It feels like this is a possible (partial) duplicate to bug 29713. Should we close the other in favor of this?
Comment 3 Lucas Gass (lukeg) 2022-01-31 14:38:25 UTC 
(In reply to Katrin Fischer from comment #2)
> It feels like this is a possible (partial) duplicate to bug 29713. Should we
> close the other in favor of this?

I would consider this one the duplicate, marking it as so.
Comment 4 Lucas Gass (lukeg) 2022-01-31 14:39:04 UTC 

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