Open Bug 95800 Opened 24 years ago Updated 11 years ago

Changing emailregexp should warn if accounts match it.

Categories

(Bugzilla :: Administration, task, P2)

Product:
Bugzilla
Component:
Administration
Version:
2.13
Type:
task

Tracking

()

People

(Reporter: CodeMachine, Unassigned)

Details

If you change the emailregexp, but accounts exist that will not match the new regexp (but matched the old one), we should display a warning, list the accounts and require confirmation. If confirmation is given we should say that you can see the invalid accounts on sanitycheck.cgi.
I'll call this a bug, not an enhancement, because it is an easy track to sanity check errors, as well as locking people out.
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.16
Moving to new Bugzilla product ...
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.13
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
OS: Linux → All
Hardware: PC → All
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being retargeted to 2.20 If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
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
This enhancement could function so slowly on installations with a large number of users.
I'm not seeing the demand for this. emailregexp is clearly billed as being about letting people in, not about policing who is in already. Gerv
You need to log in before you can comment on or make changes to this bug.