[Bug 43859] New: [NEW MODULE] Complaint and Glitch Management for Libraries
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43859 Bug ID: 43859 Summary: [NEW MODULE] Complaint and Glitch Management for Libraries Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs@lists.koha-community.org Reporter: snehasishpaul71@gmail.com QA Contact: testopia@bugs.koha-community.org Target Milestone: --- Created attachment 208520 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208520&action=edit To integrate in KOHA module PROBLEM ======= Koha currently has no dedicated module for managing operational complaints and glitches reported by library patrons or staff. When a patron encounters a system issue (e.g. OPAC search failure, circulation error, catalogue inconsistency), there is no structured way to: - Log the glitch with proper categorisation and priority - Assign it to the responsible staff member - Track resolution progress through defined workflow states - Record prevention notes on the patron record for future reference Libraries resort to ad-hoc methods: email threads, paper logbooks, or spreadsheets — all of which lack accountability, traceability, and integration with the Koha ecosystem. PROPOSED SOLUTION ================= A new "Complaint Management" module under Tools, providing: 1. Raise complaint — staff or patron submits a ticket with title, category (Catalogue, Circulation, Acquisitions, Serials, Reports, System, Other), priority (Critical/High/Medium/Low), description, and the page/module location where the glitch occurred. 2. Assign — supervisor assigns the ticket to the correct staff member. 3. Track — status workflow: Open → In Progress → Resolved → Closed. 4. Resolve — staff records a resolution note and optional patron remarks (prevention notes visible on the borrower record). 5. Comment thread — staff can add timestamped comments for discussion. 6. Dashboard — filterable list with status tabs, DataTables sorting, and per-status counts. TECHNICAL DETAILS ================= - 2 new database tables: complaints, complaint_comments - 4 new Perl modules: Koha::Complaint, Koha::Complaints, Koha::Schema::Result::Complaint, Koha::Schema::Result::ComplaintComment - 1 CGI controller: complaints/complaints.pl - 1 Template Toolkit view: complaints/complaints.tt - 1 DB revision: installer/data/mysql/db_revs/ - 1 system preference: ComplaintManagement (YesNo) - 1 sub-permission: tools > complaints - Full unit test: t/db_dependent/Koha/Complaints.t (5 subtests, 23 assertions) All code follows Koha coding guidelines: - cud- prefix on all POST operations - CSRF token validation on every form - Post-Redirect-Get pattern after mutations - i18n-ready template with [% t("...") %] wrappers - Proper DBIx::Class schema with belongs_to / has_many relationships Initial patches are ready. RFC page will be created on the wiki. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43859 Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.renvoize@openfifth.c | |o.uk --- Comment #1 from Martin Renvoize (ashimema) <martin.renvoize@openfifth.co.uk> --- This is interesting. Could you attach the changes as patch as apposed to a large gzip please I've not reviewed the code yet, but I'd like to see it build on top of the existing Tickets functionality which was built to serve this exact style of functionality. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43859 Snehasish Paul <snehasishpaul71@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #208520|0 |1 is obsolete| | CC| |snehasishpaul71@gmail.com --- Comment #2 from Snehasish Paul <snehasishpaul71@gmail.com> --- Created attachment 208565 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208565&action=edit Bug 43859: Complaint Management module — git format-patch (v2) Resubmitting as a git format-patch, as requested. This patch adds a Complaint Management module under Tools with the system preference ComplaintManagement (default: disabled). Includes ORM objects, DBIx schema, CGI controller, TT template, SQL schema, database revision, admin preference entry, and unit tests. I understand there is existing Tickets/Catalog Concerns functionality (Bug 31028). Happy to rework this to extend that system rather than building separately. Would appreciate guidance on which parts of the existing Tickets code to build upon. Key design decisions open for feedback: Should this extend the current tickets table or use a separate complaints table? Plugin vs core — what does the community prefer for this? Should the OPAC side integrate with OPACReportProblem or have its own entry point? Tested locally. All feedback welcome. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org