To prevent collisions between user-defined groups and system groups, all system groups should start with an underscore. While administrators should not be blocked from using groups beginning with an underscore, it should be understood that such names are part of the system namespace. Migration code in checksetup should check for BOTH the presence of the underscore version AND the absence of the non-underscore version before renaming.
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → administration
QA Contact: mattyt-bugzilla → default-qa
That's a pretty bad idea. We already have UI issues with products and components starting with an underscore, because Template Toolkit considers them as private keys (when used in a hash) and skip them. And TT doesn't offer any option to turn off this behavior. So till TT fixes that, assuming they want to in a future release, we should wontfix this bug.
Renaming all system groups would break many extensions and custom code. I don't see the benefit of doing this.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.