Closed
Bug 45213
Opened 25 years ago
Closed 24 years ago
Place extra word in resolve dupe error.
Categories
(Bugzilla :: Bugzilla-General, defect, P3)
Bugzilla
Bugzilla-General
Tracking
()
VERIFIED
FIXED
Bugzilla 2.12
People
(Reporter: CodeMachine, Assigned: Chris.Yeh)
References
()
Details
(Whiteboard: 2.12)
When you try to resolve a bug as a duplicate of a non-existant number, you get
the error message:
"You must specify a bug number of which this bug is a duplicate. The bug ..."
I suggest it should say "You must specify a valid bug number ..."
i'd change the wording differently than you did, but i see your point
Assignee: tara → cyeh
Whiteboard: 2.12
fixed as a part of 47790
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•24 years ago
|
||
Reopening. Your change doesn't really make sense to me. It says:
You must specify a bug number of which this bug is a duplicate or a valid bug
number. The bug has not been changed.
If it's a valid bug number, I don't need to specify a duplicate? If I specify a
bug number of which this bug is a duplicate, I don't need to specify a valid bug
number?
Or did you mean to say "of" here, but that doesn't really make sense to me
either ...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•24 years ago
|
||
Cyeh--Do you want to take this or should I try to refix it?
Comment 5•24 years ago
|
||
Okay, we came to a concensus on irc. New phrase checked in:
You must specify a valid bug number of which this bug is a duplicate. The bug
has not been changed.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
Comment 6•24 years ago
|
||
Aargh! Wait! The code which populates the duplicates table when it is created
(say, for example, you are upgrading an old Bugzilla installation) searches for
this string in the comments as part of its method of populating that table.
That code (in checksetup.pl) will have to be modified so that it only searches
for the common string between the old and new versions. Reopening this bug to
track that issue.
Gerv
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 7•24 years ago
|
||
This change doesn't effect the database at all. It is a "display on error" only.
Updating the URL field to have the link to bonsai so you can easily see the patch.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 8•24 years ago
|
||
Oops, sorry. I panicked before I read the entire thing. I thought you were
altering the "*** This bug has been marked a duplicate of..." string.
<goes back to sleep>
Gerv
Comment 10•24 years ago
|
||
In search of accurate queries.... (sorry for the spam)
Target Milestone: --- → Bugzilla 2.12
Comment 11•24 years ago
|
||
Moving closed bugs to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•