Closed
Bug 408097
Opened 17 years ago
Closed 14 years ago
unique user-matching still prompts that requests might have been lost
Categories
(bugzilla.mozilla.org :: General, defect)
bugzilla.mozilla.org
General
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: justdave, Unassigned)
Details
filing this here because I think we backported this feature for b.m.o and I'm not sure if it exists upstream or only in our backport. We can move it to Bugzilla if it turns out to be upstream.
STR:
1) File a bug and add an attachment at the same time. On that attachment, put in an incomplete email address for the requestee on a flag, but enough of it to uniquely match someone
results:
get a prompt on filing saying that some of the requests may have been lost. Notice that none of them were.
I suspect this happens because the user matching triggers at all, but in the case of a unique match, it doesn't have to prompt the user, so it really did suceeed.
Comment 1•17 years ago
|
||
Yeah, that almost certainly doesn't happen upstream.
It could also be because you're running some random point on the branch, and not an actual release.
Reporter | ||
Comment 2•17 years ago
|
||
Rearranging this component to not have me as the default assignee, so that it doesn't appear like I'm intending to work on bugs that other people could be taking care of if they didn't think I was already doing them. If this bug is a software issue on b.m.o and you'd like to fix it, the modified source is now available for the patching (see bug 373688). Reassigning to the new default owner.
Assignee: justdave → nobody
QA Contact: reed → other-bmo-issues
Comment 3•14 years ago
|
||
Following Dave's steps to reproduce, I no longer get a warning message if my string is specific enough to match only one person.
Gerv
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•14 years ago
|
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•