Bug 22926 - Use standard columns configuration on batch item modification and delete pages
Summary: Use standard columns configuration on batch item modification and delete pages
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Tools (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-16 12:55 UTC by Owen Leonard
Modified: 2025-02-05 19:07 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Owen Leonard 2019-05-16 12:55:13 UTC
The custom column configuration system built for batch item modification and batch item deletion predates the addition of DataTable column configuration. I don't think there's any reason to keep it, and making things standard is good.
Comment 1 Noémie Labine 2023-05-05 13:05:34 UTC
That would be nice ! 

When we hide columns in batch item modification/batch item deletion, the hiddens columns will stay hidden in the next batch modification or deletion (tho currently there's a bug for that in bz32477).

But when our browser cache is renewed, those choices are reinitialised and all the colums are showned. Having the choice to permanently hide some columns by adding those tool to the column configuration would save time when we always hide one or more columns.
Comment 2 Emmi Takkinen 2024-12-18 10:11:21 UTC
+1 for this. Those filters seem to be constantly broken when new columns are added and using DataTable configuration would make them easier to maintain.
Comment 3 Emmi Takkinen 2024-12-18 10:38:48 UTC
This would also mean that we can get rid of using same code for both of these tables which has caused us problems with "Show/Hide all" selection (see bug 36129). And it seems to cause them still despite fix in bug 36129. Also we have again same problem as in bug 32477, nut this time with item status columns.