| Summary: | The "select a specific item" table on opac-reserve.tt should be column configurable | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Lucas Gass (lukeg) <lucas> |
| Component: | OPAC | Assignee: | Lucas Gass (lukeg) <lucas> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | ||
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | Small patch |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | 29899 | ||
| Bug Blocks: | |||
| Attachments: | Bug 29972: Make the select a specific item table configurable on opac-reserve.tt | ||
|
Description
Lucas Gass (lukeg)
2022-01-28 21:09:22 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. It feels like this is a possible (partial) duplicate to bug 29713. Should we close the other in favor of this? (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. |