October 2016 - Koha-bugs - lists.koha-community.org

[Bug 15976] New: test bug for a script we are developping.
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15976 Bug ID: 15976 Summary: test bug for a script we are developping. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: remi.mayrand-provencher(a)inLibro.com Reporter: remi.mayrand-provencher(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org CC: remi.mayrand-provencher(a)inLibro.com -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 15892] New: branchtransfer from branch is set to the transferred Item's holding branch, not the current loggedinbranch from where the transfer originates
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15892 Bug ID: 15892 Summary: branchtransfer from branch is set to the transferred Item's holding branch, not the current loggedinbranch from where the transfer originates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com REPLICATE ISSUE: 1. Check-out an Item from branch A 2. Change loggedinbranch to branch B 3. Initiate a branchtransfer from branch B to branch C 4. Observe the Item's holdingbranch to be branch A. If one sends the Item from branch B to branch C, how can it's last branch where it was detected be branch A? It should be branch B since that is where the Item currently physically is. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 15873] New: Restrict patron to hold those items which already checked-out by them.
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15873 Bug ID: 15873 Summary: Restrict patron to hold those items which already checked-out by them. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: amitddng135(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Restrict patron to hold those items which already checked-out by them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 15862] New: Cataloging editor should gracefully handle unknown biblionumbers
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15862 Bug ID: 15862 Summary: Cataloging editor should gracefully handle unknown biblionumbers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you try to open a record in the basic MARC editor by passing bad or deleted biblionumber you get an error: Can't call method "title" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 827. We should show a friendlier error message to the user. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 15857] New: Add test mode to process_message_queue.pl
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15857 Bug ID: 15857 Summary: Add test mode to process_message_queue.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice for testing and migration purposes if we could run process_message_queue.pl but have the emails go to a testing address instead of the patron's email address, and have SMS messages go to a testing phone number instead of the patron's sms number. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 15767] New: Add ordering capability to batch
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15767 Bug ID: 15767 Summary: Add ordering capability to batch Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org A batch should be ordered as desired. Currently the order is given by the sequence the patrons are entered into the list. That sequence is not shown again but defines the arrangement of the patroncards on the sheet. Staff trying to hand out new patron cards need to find these on the sheets. Staff would really appreciate if there was a reliable and obvious order. Implementing ordering has nothing to do with the current feature that batches can be displayed ordered according to currently shown names or card numbers. The display feature is helping to check the batch but is not creating order on the sheets. Implementing ordering should start with entry order but should allow to reorder list items, e.g. to shift a patron that was missing initially and added later into the desired position. Ordering by barcode or by surname are other likely choices. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 15724] New: Add possibility to export notice in marc format in z39.50 results
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15724 Bug ID: 15724 Summary: Add possibility to export notice in marc format in z39.50 results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, Preview marc of a notice exist in a Z39.50 list result, but it would be great to have a way to export file in format marc. This file can then be processed in MarcEdit. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 15678] New: Make pickup branch editable on holds tab on circulation/patron detail screens
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15678 Bug ID: 15678 Summary: Make pickup branch editable on holds tab on circulation/patron detail screens Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 9528 added a pickup at column to the holds tab on the circulation/patron detail screens. Liz Rea mentioned, "it should be editable without deleting and re-adding the reserve." I'm filing a new bug with that suggestion. That would be quite useful to have. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 16688] New: RenewSerialAddsSuggestion - suggestions not showing up, note not saved
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '19

16 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16688 Bug ID: 16688 Summary: RenewSerialAddsSuggestion - suggestions not showing up, note not saved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When renewing a serial subscription with RenewSerialAddsSuggestion set to active, an entry is added to the suggestions table in Koha. The status is "ASKED" and the biblionumber is column is set to the existing record. But the suggestion isn't shown in the acquisition module - it cannot be found using the search options in suggestions, it doesn't show in the pending tab. Because the status is "ASKED", there is no way to create an order for it. When renewing the subscription, there is a note field you can fill out "for the librarian to process the order" - but this information is not stored in suggestion table and seems to be lost. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 17160] New: Foreign key constraint for message_transports is too loose
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '19

16 Dec '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17160 Bug ID: 17160 Summary: Foreign key constraint for message_transports is too loose Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I think this is the probable cause for Bug 13171. http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=installer/data/my… The message transports definition -- -- Table structure for table `message_transports` -- DROP TABLE IF EXISTS `message_transports`; CREATE TABLE `message_transports` ( `message_attribute_id` int(11) NOT NULL, `message_transport_type` varchar(20) NOT NULL, `is_digest` tinyint(1) NOT NULL default '0', `letter_module` varchar(20) NOT NULL default '', `letter_code` varchar(20) NOT NULL default '', `branchcode` varchar(10) NOT NULL default '', PRIMARY KEY (`message_attribute_id`,`message_transport_type`,`is_digest`), KEY `message_transport_type` (`message_transport_type`), KEY `letter_module` (`letter_module`,`letter_code`), CONSTRAINT `message_transports_ibfk_1` FOREIGN KEY (`message_attribute_id`) REFERENCES `message_attributes` (`message_attribute_id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `message_transports_ibfk_2` FOREIGN KEY (`message_transport_type`) REFERENCES `message_transport_types` (`message_transport_type`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `message_transports_ibfk_3` FOREIGN KEY (`letter_module`, `letter_code`, `branchcode`) REFERENCES `letter` (`module`, `code`, `branchcode`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; Has `message_transport_types` (`message_transport_type`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `message_transports_ibfk_3` FOREIGN KEY (`letter_module`, `letter_code`, `branchcode`) REFERENCES `letter` (`module`, `code`, `branchcode`) ON DELETE CASCADE ON UPDATE CASCADE The foreign key contstraints `module`, `code`, `branchcode` do *NOT* uniquely identify a row in the letter table, because message_transport_type may vary. Therefore, a deletion *any* message transport type will delete *all* rows matching `module`, `code`, `branchcode`. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7