[Koha-bugs] [Bug 11889] Disown a list
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Thu Jun 9 12:06:24 CEST 2022
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11889
Marcel de Rooy <m.de.rooy at rijksmuseum.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|BLOCKED |Signed Off
CC| |martin.renvoize at ptfs-europe
| |.com
--- Comment #86 from Marcel de Rooy <m.de.rooy at rijksmuseum.nl> ---
This was reported by myself in 2014 !
And Aleisha did a brave attempt to get this in in 2017. And then we started a
discussion that kept this development in permafrost until now. And it will
probably will stay there if we want to address all issues reported here.
I would really love to get this further now. So I would propose the following:
[1] Aleisha has 2 patches here, rest I added. There was already a signoff but
since I added and refreshed it now, I take the signoff and ask for another QAer
to have a look. Martin or Jonathan perhaps?
[2] This development allows you to choose between current behavior or move
ownership of public and shared lists to the staff member deleting a user. If
you dont like transferring ownership like this, do not yet enable the pref. The
fact that we have this pref, allows us to push this on its own.
Important: note that deleting users with cron in an 'anonymized workflow' will
still lead to deleting lists. We should still address that on a new report!
Bug 30933. Allowing to designate a special user as owner.
[3] We still need a separate transfer ownership feature. Will try to add some
code on bug 25498.
With [2] and [3] I think we covered all concerns in the discussion here,
providing a foundation for several workflows with or without specially
designated users for general lists.
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list