Closed
Bug 61634
Opened 24 years ago
Closed 23 years ago
describe Milestone URL in edit products page
Categories
(Bugzilla :: Administration, task, P2)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.16
People
(Reporter: hansoneric, Assigned: CodeMachine)
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
caillon
:
review+
justdave
:
review+
|
Details | Diff | Splinter Review |
It would be nice if the description for the "target milestone url" (on the edit
products page) field was more explicit. Or if the title linked to a more
complete descption such as "URL to a page you create for explaining the target
miletones". Or even as a default to the notargetmilestone.html page.
Reporter | ||
Comment 2•24 years ago
|
||
Sorry for the brevity, it made sense to me at the time :) On the edit products
page there is a field labeled "Milestone URL:". It is a url to a file that
describes what the milestones are for each product. The url is used to create a
link when viewing a bug, the words "Target Milestone", next to the pull down
list, becomes a link that takes you to the page you specify in the "Milestone
URL:". I found that the words "Milestone URL:" were insufficient to describe
the above effects. I think that if the notargetmilestone.html file that is
included with bugzilla where the default entry in this field whenever a
componenet was created, it would be more intuitive and clearer.
1) It would then create the link on every bug so that you wouldn't have the
erratic behavior of "Target Milestone" sometimes being a link and other times
not. Currently if the "Milestone URL:" field is empty, no link is created.
2) This could also be resolved by a short paragraph that describes what in blue
blazes the "Milestone URL:" on the edit products page does.
Hope this helps clear this up. I think this would be an easy fix, depending on
what method is implemented (both preferably). I might even patch this myself
when i get time :)
Assignee | ||
Comment 3•24 years ago
|
||
"Milestones Description URL" ?
Updated•24 years ago
|
Whiteboard: 2.14 → 2.16
Reporter | ||
Comment 4•24 years ago
|
||
why so far into the future for such a minimal change?
Comment 5•24 years ago
|
||
because 2.12 is locked on new features in order to get it out, and 2.14 is going
to be a security update designed to seal a lot of the holes in bugzilla
currently, thus, only bugs which affect security are being considered for 2.14.
Comment 7•23 years ago
|
||
this could use a more descriptive summary. not wanting to step on toes and
change a field that I don't own I'll leave it up to the assignee or QA contact.
I suggest something like "describe Milestone URL in edit products page" or
something like that.
Updated•23 years ago
|
Summary: Small change for target milestones → describe Milestone URL in edit products page
Assignee | ||
Updated•23 years ago
|
Priority: P3 → P1
Whiteboard: 2.16
Comment 8•23 years ago
|
||
moving
Assignee: tara → justdave
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: other → 2.10
Assignee | ||
Comment 9•23 years ago
|
||
Assignee | ||
Updated•23 years ago
|
Severity: enhancement → minor
OS: Linux → All
Hardware: PC → All
Comment 10•23 years ago
|
||
Comment on attachment 58505 [details] [diff] [review]
Change description to "URL That Describes Milestones To Users".
I would prefer "URL Describing Milestones For This Product:".
Attachment #58505 -
Flags: review-
Assignee | ||
Comment 11•23 years ago
|
||
Attachment #58505 -
Attachment is obsolete: true
Assignee | ||
Updated•23 years ago
|
Severity: minor → normal
Priority: P1 → P2
Comment 12•23 years ago
|
||
Comment on attachment 58845 [details] [diff] [review]
Again.
r=caillon.
I like the wording.
Attachment #58845 -
Flags: review+
Comment 13•23 years ago
|
||
Comment on attachment 58845 [details] [diff] [review]
Again.
r= justdave
Attachment #58845 -
Flags: review+
Comment 15•23 years ago
|
||
/cvsroot/mozilla/webtools/bugzilla/editproducts.cgi,v <-- editproducts.cgi
new revision: 1.21; previous revision: 1.20
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 16•22 years ago
|
||
*** Bug 136146 has been marked as a duplicate of this bug. ***
Updated•12 years ago
|
QA Contact: jake → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•