| Summary: | Holds to pull: check button Solved by | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Michal Denar <black23> |
| Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | black23, gmcharlt, josef.moravec, kyle.m.hall, rbit |
| Version: | 16.05 | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Michal Denar
2016-11-01 13:36:49 UTC
Once the hold is waiting or in transport it should no longer show on the list - can you explain what happens for you with a test plan a bit more? (In reply to Katrin Fischer from comment #1) > Once the hold is waiting or in transport it should no longer show on the > list Does this bug refer instead to the holds queue report (circ/view_holdsqueue.pl) ? Since that one is generated periodically I can see how marking something as "solved" would be useful. Hello Katrin, I agree with you generally. But some libraries have braches and stores. In these cases is process different. Let me expain it on example: - borrower hold to pull title from external store without staff - somebody from staff at main bulding create request for driver - hold is still on list but without any sign that request is already done - if staff members rotate very often do same work because dont know that request is done, so we need some paper solution or help from Koha I agree that can be option function for some libraries. Mike *** This bug has been marked as a duplicate of bug 18463 *** (In reply to Mike from comment #3) > Hello Katrin, > I agree with you generally. But some libraries have braches and stores. In > these cases is process different. Let me expain it on example: > - borrower hold to pull title from external store without staff > - somebody from staff at main bulding create request for driver > - hold is still on list but without any sign that request is already done > - if staff members rotate very often do same work because dont know that > request is done, so we need some paper solution or help from Koha > > I agree that can be option function for some libraries. > > Mike Hi Mike, thx for explaining your use case - this helps a lot to be able to understand your needs! |