Bug 26241 - HoldsQueueSkipClosed blocks updates to Transport Cost Matrix
Summary: HoldsQueueSkipClosed blocks updates to Transport Cost Matrix
Status: RESOLVED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-18 17:32 UTC by Christopher Brannon
Modified: 2023-09-22 19:59 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2020-08-18 17:32:07 UTC
When HoldsQueueSkipClosed is set to Closed, it will disable libraries in the Transport Cost Matrix that are closed.  This is fine, except it makes it impossible to update the values of closed libraries.  You either have to wait until the library is not closed to update the value or set HoldsQueueSkipClosed to Open and Closed, updated values in the matrix, and set HoldsQueueSkipClosed back to Closed.

If you try to update the matrix while HoldsQueueSkipClosed is set to Closed by enabling the disabled value, you are not shown the previous value.  If you set a value, it does save, but when you refresh the page, the value is disabled.  This is not a problem in itself, but the process is confusing.  It took me a long time to discover that the HoldsQueueSkipClosed preference was controlling the matrix.

* It would be preferred if the HoldsQueueSkipClosed preference noted that it controls the enabling and disabling of the matrix.
* It would be preferred if the matrix noted on the page that it was being controlled by the HoldsQueueSkipClosed preference.
* It would be preferred that disabling a value in the matrix didn't hide the value of that is disabled.
* It would be preferred that the matrix could be updated without having to enable a value first.  Values and disabling should be independent.
Comment 1 Kyle M Hall 2020-08-25 16:48:05 UTC
I've been trying to recreate this issue and so far I have been unable to. Christopher, could you make a screencast demonstrating the issue?

Thanks!
Comment 2 Katrin Fischer 2023-09-22 19:59:36 UTC
(In reply to Kyle M Hall from comment #1)
> I've been trying to recreate this issue and so far I have been unable to.
> Christopher, could you make a screencast demonstrating the issue?
> 
> Thanks!

Closing WORKSFORME for now, please reopen if you can still reproduce the issue.