https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43301
--- Comment #2 from David Cook <[email protected]> --- (In reply to Olivia Reynolds from comment #1) > I've experimented with making the behaviour more logical, but every change > I've > made has failed an explicit group permission test somewhere which makes me > worry > people depend on the current implementation. For example, > `t/db_dependent/Koha/Patrons.t` line 1898 asserts that you can only see your > library if it's not in a group, and line 1847 asserts you can see libraries > outside of your group if that group doesn't have the relevant feature. I have that same worry... People depend on the current implementation. The current implementation has incorrect behaviour. Thus, people depend on an implementation with incorrect behaviour. People depend on the implementation's incorrect behaviour. The incorrect behaviour can be changed. Therefore, changing the implementation will affect the behaviour people depend on. And on we go... -- I suppose one solution is to change the behaviour, but only for the next major release. That we don't backport the change, and we make sure the release notes *clearly states* that user data visibility will change. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
