#36793: Reverting a model rename in an environment with pre-Django 6.0
permission
records leaves wrong users & groups associated
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Artyom
| Kotovskiy
Type: Bug | Status: assigned
Component: contrib.auth | Version: 6.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Clifford Gama):
I share your position, Jacob and Antoliny.
That user 2 does not have the permissions is definitely a bug in 6.0, so
that needs to be fixed and backported.
Whether user 1 also ends up having the permissions should depend on
whether that was the behavior before the patch in #27489 landed. If it
wasn't then it would need a new-feature-like release note, meaning it
cannot be backported. If it was, then it should be fixed as a regression
in a new feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/36793#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b133181be-8f74de91-9024-486f-ab8f-e997ac01d6cc-000000%40eu-central-1.amazonses.com.
