Closed Bug 76864 Opened 25 years ago Closed 21 years ago

new and edit component pages have inconsistant errors for bad owner

Categories

(Bugzilla :: Administration, task, P3)

2.11

Tracking

()

RESOLVED INVALID

People

(Reporter: CodeMachine, Unassigned)

Details

When I enter a bad component owner for a new component, it says: The name bdsdfg@sdfsd.net is not a valid username. Either you misspelled it, or the person has not registered for a Bugzilla account. When I change the component owner to a bad address, it says: Sorry, you must use an existing Bugzilla account as initial owner. These are inconsistent - they should be the same message. I suggest the first is better, especially because it specifies what was typed.
Target Milestone: --- → Bugzilla 2.16
Based on the description, it sounds like creating a component uses DBID_to_name_and_check() [possibly spell a little different] and changing uses it's own name converstion/error checking.
Priority: -- → P3
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: Bugzilla 2.11 → 2.11
-> component owner of the new Bugzilla product
Assignee: tara → justdave
Summary: Inconsistent messages. → new and edit component pages have inconsistant errors for bad owner
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
All 2.18 bugs that haven't been touched in over 60 days and aren't flagged as blockers are getting pushed out to 2.20
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
Looking at Bonsai, it appears that the error message has always been consistent when adding or editing a component, see the link below and bug 66876 which introduces these checks for the first time. Marking this bug as invalid. http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=editcomponents.cgi&branch=1.15&root=/cvsroot&subdir=mozilla/webtools/bugzilla&command=DIFF_FRAMESET&rev1=1.15&rev2=1.16
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.