[Koha-bugs] [Bug 24008] New: No warning is produced when trying to delete a patron with credit (patron is not deleted)

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Mon Nov 11 13:32:28 CET 2019


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

            Bug ID: 24008
           Summary: No warning is produced when trying to delete a patron
                    with credit (patron is not deleted)
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Patrons
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: martin.renvoize at ptfs-europe.com
        QA Contact: testopia at bugs.koha-community.org
                CC: fridolin.somers at biblibre.com, gmcharlt at gmail.com,
                    jonathan.druart at bugs.koha-community.org,
                    katrin.fischer at bsz-bw.de, kyle.m.hall at gmail.com,
                    martin.renvoize at ptfs-europe.com,
                    testopia at bugs.koha-community.org, theod at lib.auth.gr,
                    tomascohen at gmail.com, victor.grousset at biblibre.com
        Depends on: 23822

+++ This bug was initially created as a clone of Bug #23822 +++

When one tries to delete a patron that has a credit in his account, no warning
is produced. 
The deletion is not performed (which is the proper behavior), however one would
expect to see a warning similar to the one that is produced when the patron has
an unpaid fine, a checked out item, a hold, etc.

The following screencast was performed in ByWaters' sandboxes running 19.05 and
shows the issue:
https://screencast-o-matic.com/watch/cq6D6vu4YJ


Referenced Bugs:

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23822
[Bug 23822] No warning is produced when trying to delete a patron with credit
(patron is not deleted)
-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.


More information about the Koha-bugs mailing list