[Koha-bugs] [Bug 28520] New: Cancelling a hold that is in transit hides item's transit status

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28520

            Bug ID: 28520
           Summary: Cancelling a hold that is in transit hides item's
                    transit status
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: critical
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: joonas.kylmala at helsinki.fi
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com, martin.renvoize at ptfs-europe.com,
                    nugged at gmail.com, stalkernoid at gmail.com

When you cancel a hold that is in transfer to another branch the transfer
status disappears from the item info. In the database you can see following
transfers created for the items after the cancellation:

> mysql> select * from branchtransfers\G
> *************************** 1. row ***************************
>   branchtransfer_id: 1
>          itemnumber: 549
>       daterequested: 2021-06-07 08:11:05
>            datesent: 2021-06-07 08:11:05
>          frombranch: MPL
>         datearrived: NULL
>       datecancelled: 2021-06-07 08:13:22
>            tobranch: CPL
>            comments: NULL
>              reason: Reserve
> cancellation_reason: CancelReserve
> *************************** 2. row ***************************
>   branchtransfer_id: 2
>          itemnumber: 549
>       daterequested: 2021-06-07 08:13:22
>            datesent: NULL
>          frombranch: MPL
>         datearrived: NULL
>       datecancelled: NULL
>            tobranch: MPL
>            comments: NULL
>              reason: TransferCancellation
> cancellation_reason: NULL

The code in koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/detail.tt and
catalogue/detail.pl checks whether $transfertwhen is defined but since this new
code seems to create a transfer *request* there is not yet a
datesent/transfertwhen created and so the transfer is not displayed.

Bumbing priority to critical because this leads to librarians think
availability of an item is different than what in reality it is and could cause
miscommunication between the library and patrons.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.