| Summary: | Conflicting behaviour of the columns visibility on the items table | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Jonathan Druart <jonathan.druart> |
| Component: | Staff interface | Assignee: | Jonathan Druart <jonathan.druart> |
| Status: | ASSIGNED --- | QA Contact: | Testopia <testopia> |
| Severity: | major | ||
| Priority: | P5 - low | CC: | caroline.cyr-la-rose, gmcharlt, schodkowy.omegi-0r |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38391 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38436 |
||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | 33484, 38482, 38485 | ||
| Bug Blocks: | |||
|
Description
Jonathan Druart
2024-11-13 15:25:49 UTC
What do we do? One solution would be to prevent the state to be restored for this table and disable the option from the admin config page. We also need to fix bug 38391 here. *** This bug has been marked as a duplicate of bug 38436 *** On that note, as I understand this behavior hasn't been changed so far yet:
> Then you have the "hide the column if no data to display" behaviour
It would be nice if this was re-computed on every page change too.
It's a bit confusing if going to page 2, and certain non-empty columns now remain hidden, because they keep the initial empty column hiding settings from page 1, I know this has confused some users.
And currently the only dirty workaround is to increase how many items are loaded at once and cross fingers that all the used columns won't happen to be empty on page 1 then... But there are very often cases where just a single item would have some column populated in a very long item list, for one reason or another. And that fact would remain completely concealed to the librarian in the default view, even though it's visible in OPAC unbeknownst to them...
If column visibility changing logic is to be re-coded in a more smart fashion, it would be very nice to fix that thing as well at the same time.
(In reply to Michał from comment #5) > On that note, as I understand this behavior hasn't been changed so far yet: > > > Then you have the "hide the column if no data to display" behaviour > > It would be nice if this was re-computed on every page change too. > > It's a bit confusing if going to page 2, and certain non-empty columns now > remain hidden, because they keep the initial empty column hiding settings > from page 1, I know this has confused some users. > > And currently the only dirty workaround is to increase how many items are > loaded at once and cross fingers that all the used columns won't happen to > be empty on page 1 then... But there are very often cases where just a > single item would have some column populated in a very long item list, for > one reason or another. And that fact would remain completely concealed to > the librarian in the default view, even though it's visible in OPAC > unbeknownst to them... > > If column visibility changing logic is to be re-coded in a more smart > fashion, it would be very nice to fix that thing as well at the same time. This will be fixed on 24.11. |