https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27781 Bug ID: 27781 Summary: Editing Codes Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs@lists.koha-community.org Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com I understand the need to not allow code editing once a code has been created for tables. However, I am wondering if we could consider another approach. It is risky, but might provide more flexibility with editing. This would be particularly helpful to those of us that mistype a code, or create a code, only to realize that sorting in dropdowns is based on order of the code, not the description. What if we added an option to change the code, and the process would A) check related tables to make sure the suggested change doesn't already exist, and B) change all instances of that code in related tables. If there are flaws with this process, or it is too risky, I understand. I am just one of those people that hates it when you make a mistake and then it lives in your database for eternity. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.