Closed
Bug 71406
Opened 25 years ago
Closed 11 years ago
Time to upgrade "how to find previously reported bugs"
Categories
(Developer Documentation Graveyard :: General, defect)
Developer Documentation Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: sidr, Assigned: sheppy)
References
()
Details
(Whiteboard: p=0 u=webdev c=MDN)
Attachments
(2 files)
|
15.29 KB,
text/html
|
Details | |
|
10.68 KB,
patch
|
Details | Diff | Splinter Review |
Summary:
It's time to update
http://www.mozilla.org/quality/help/beginning-duplicate-finding.html
to make it conform better to the style and substance of
Bugzilla documentation written since, and make sure it works with
Bugzilla 2.12.
Two proposed changes:
> It might be useful to add a link to View Bugs Already Reported Today.
... in paragraph 2, sentence 1.
As with http://www.mozilla.org/bugs/text-searching.html and
http://bugzilla.mozilla.org/showattachment.cgi?attach_id=27041 (bug 16775):
more show, less tell: show snippets of the query form demonstrating
how to fill in that part of the form, rather than relying on description.
This should increase precision and cut down on verbiage.
At the same time, ensure that both the description and form-filling
exmples match Bugzilla 2.12's new query page.
( sample: http://bugzilla.mozilla.org/showattachment.cgi?attach_id=25800 )
Comment 1•25 years ago
|
||
Sounds great :-) Attach a new version and I'll review and check it in.
Gerv
| Reporter | ||
Comment 2•25 years ago
|
||
Notes:
1. Add davidr8@home.com (Jesse Ruderman) to cc: list as soon as there's
something to see. If you read this first, Jesse, you did a great job
reviewing the Text Searching/Regex doc; if you can do the same here...
2. Make sure that all example forms are inoperable and variables are unique.
3. Wait on bug 16775 to reword *Doing the Query* Section to match the new
query.cgi section order. (Dependency added for notification.) Likely 2.13?
4. Do something about dual-audience problem. One audience has used bugzilla
before, and is probably using a nightly or CVS build; todays bugs are
relevant to them. The other is trying to query bugzilla for the first
or second time (outside the confines of the Bugzilla Helper) and is
probably using a milestone; today's bugs won't be relevant to them,
but they could use more detailed instructions than the former audience.
Split into finding-duplicate-bugs.html and beginning-duplicate-finding.html
(respectively) for the two audiences? Handle some other way?
5. Split paragraph 2 at the sentence boundary?
Status: NEW → ASSIGNED
Depends on: 16775
accepting QA for mozilla developer docs.
some of these bugs have been around for a _long_ time. Reporters, would you
please review the bugs, see if the issues have been resolved, and close bugs
appropriately.
I will do a full review of all bugs not touched in one week (8th April).
Thanks.
</spam>
QA Contact: endico → imajes
Comment 4•23 years ago
|
||
related: bug 149912
Comment 5•23 years ago
|
||
This bug is decrepit and obsolete IMO.
Gerv
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Updated•22 years ago
|
Status: RESOLVED → REOPENED
QA Contact: imajes → daniel.bugmail
Resolution: INVALID → ---
Comment 6•22 years ago
|
||
add gerv as the page maintainer & date the document
update for Bugzilla interface changes
suggest using Resolution instead of Status for bug searches
some text & markup touch-ups
Comment 8•22 years ago
|
||
Daniel: best if you attach the entire new file rather than a patch; it's easier
to review that way.
Gerv
Comment 9•22 years ago
|
||
Comment on attachment 159169 [details]
HTML v1
guess I already did ;-)
Attachment #159169 -
Attachment description: patch v1 → HTML v1
Attachment #159169 -
Attachment is obsolete: false
Attachment #159169 -
Attachment is patch: false
Attachment #159169 -
Attachment mime type: text/plain → text/html
Updated•19 years ago
|
Assignee: sidr → nobody
Status: REOPENED → NEW
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
QA Contact: danielwang → doc-request
Updated•14 years ago
|
Component: Documentation Requests → Documentation
Comment 10•13 years ago
|
||
Automatically closing all bugs that have not been updated in a while. Please reopen if this is still important to you and has not yet been corrected.
Status: NEW → RESOLVED
Closed: 23 years ago → 13 years ago
Resolution: --- → INVALID
Comment 11•13 years ago
|
||
Reopening for review by Sheppy.
Assignee: nobody → eshepherd
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
| Assignee | ||
Comment 12•13 years ago
|
||
We should put this content into https://developer.mozilla.org/en-US/docs/Mozilla/ somewhere - maybe like https://developer.mozilla.org/en-US/docs/Mozilla/QA/Finding_previously_reported_bugs
Updated•13 years ago
|
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Comment 13•13 years ago
|
||
Am I correct in assuming that this bug is now referring to the MDN page "Screening duplicate bugs"? If that is the case, the Summary and URL should be updated to reflect that. (https://developer.mozilla.org/en-US/docs/Screening_duplicate_bugs)
| Assignee | ||
Updated•13 years ago
|
Whiteboard: p=0 u=webdev
| Assignee | ||
Updated•13 years ago
|
Whiteboard: p=0 u=webdev → p=0 u=webdev c=MDN
Comment 14•11 years ago
|
||
I'm closing this. If you disagree, open a *new* one with the relevant information of something (left) to do. Reading this bug and understand what is left to do is impossible.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 11 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•