June 2019 - Koha-bugs - lists.koha-community.org

[Bug 7890] Required fields in the MARC editor should be highlighted
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7890 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|22399 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22399 [Bug 22399] Improve responsive behavior of the basic marc editor -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6993] Incorrect data type in auth_subfield_structure
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6993 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- *** This bug has been marked as a duplicate of bug 22919 *** -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 17978] New: Circ rules will not limit holds
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17978 Bug ID: 17978 Summary: Circ rules will not limit holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It appears that the holds limit in circ rules is broken. I can set a limit of 0 on holds and it will block the hold, but if I set it to anything higher than 0, it ignores the value altogether and gives the patron unlimited holds. Maxreserves works as expected. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 22980] New: Unwanted console.log in simple MARC editor template
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22980 Bug ID: 22980 Summary: Unwanted console.log in simple MARC editor template Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 22045 Target Milestone: --- Bug 22045 added some debugging in the form of a console.log() which shouldn't have made it into the final version. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22045 [Bug 22045] Cataloging UX enhancement - Improve access to tabs -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7890] Required fields in the MARC editor should be highlighted
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

1 0

[Bug 23161] New: We need to document the release process for this project?
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23161 Bug ID: 23161 Summary: We need to document the release process for this project? Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb (server) Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com Target Milestone: --- Right now I just have lots of questions: 1) What do we envisage the process for bugfixes being? (reported in gitlab or bugzilla or synced between the two?) 2) What do we envisage the process for enhancements being? (reported gitlab or bugzilla or synced between the two?) 3) Do we follow the same Testing/SO/QA process? 4) Are we running one and only one instance of Mana or are we running different versions in parallel to support the different koha versions that will be out there in the world? 5) Who is responsible for merging once a bug/enhancement has been given the go ahead? 6) When do releases happen (in step with Koha releases?) 7) What is our policy on breaking changes? 8) Should we have a deployment pipeline triggered via merges to master? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 23160] New: No limit when searching
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23160 Bug ID: 23160 Summary: No limit when searching Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb (server) Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com Target Milestone: --- Imported from gitlab issues (Joubu) There are currently 301 reports in the Mana DB. You can search '' and retrieve all of them. We will certainly need a hardcoded limit (server-side) at some point, to prevent the server to crash -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 6812] Configure enrollment, renewal, duplicate card, hold fees by branch and patron category
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6812 Tomáš Wünsch <fraktik(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fraktik(a)gmail.com, | |josef.moravec(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 19247] New: Feature release change tool
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19247 Bug ID: 19247 Summary: Feature release change tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 13640] Holds To Pull List includes items unreserveable items
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '19

19 Jun '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13640 --- Comment #16 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- (In reply to Jonathan Druart from comment #15) > (In reply to Martin Renvoize from comment #12) > > (In reply to Jonathan Druart from comment #10) > > > Because there are 3 values: From any library, From home library and not > > > allowed (0) > > > > I'm wondering if we're taking into account the 1, and 2 options correctly > > then in that case? > > Why not? The patch adds the holdallowed != 0 condition, which matches 1 and > 2 :) It was more of a 'note to self' to make sure I improved my understanding of how the value is used before Signing Off. It looks sane enough to me, but I'm still not 100%. What I'm trying to work out is if the clause is in the right place and is indeed correct allowing both 1 and 2 options. I note that with independent branches switched on we limit by holdingbranch being the local branch.. hence wondering if we aught to be handling library limitations in this part of the query too... It's one monster query. -- You are receiving this mail because: You are watching all bug changes.

1 0