Closed
Bug 355302
Opened 18 years ago
Closed 18 years ago
Documentation for the "clone bug" feature
Categories
(Bugzilla :: Documentation, enhancement)
Bugzilla
Documentation
Tracking
()
RESOLVED
FIXED
Bugzilla 2.20
People
(Reporter: dmullins, Assigned: spam)
References
Details
Attachments
(2 files, 1 obsolete file)
(deleted),
patch
|
goobix
:
review+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
goobix
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Build Identifier: bugzilla 2.22.2
I downloaded the Bugzilla Guide - 2.20.2 Release in PDF format and used the binocular tool from Adobe's reader with the words "clone" and "cloning". The results from these two searches is NULL.
i also read the chapter 6 entitled "Using Bugzilla". there is no information about the use or purpose of Cloning a Bug, the effect cloning will have on a bug database, the result of closing the Parent Bug on the the cloned Child bug, etc.
Reproducible: Always
Steps to Reproduce:
1.down load the Bugzilla Guide - 2.20.2 Release in PDF format
2.use the binocular tool from Adobe's reader with the words "clone" and "cloning".
3. the search results will be null.
Expected Results:
some explanation in the Bugzilla Guide about "Cloning" and its intended purpose(s)
Comment 1•18 years ago
|
||
That's true--there's lots of features that don't have documentation. We could use some volunteer assistance there! :-)
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Summary: in The Bugzilla Guide - 2.20.2 Release there is NO descriptive info on CLONING a Bug → Documentation for the "clone bug" feature
Assignee | ||
Comment 2•18 years ago
|
||
Attachment #246450 -
Flags: review?(documentation)
Comment 3•18 years ago
|
||
Comment on attachment 246450 [details] [diff] [review]
docs patch for tip
@@ -999,6 +999,21 @@
bugs in the tree (that don't have further dependencies).
</para>
</section>
+
+ <section id="clonebug">
I'd probably put this new section right after the "Filing Bugs" thing.
+ <title>Clone Bug</title>
-> "Clone Bugs"
+ Since 2.20
"Starting with version 2.20"
> Bugzilla have a feature -> "Bugzilla has a feature"
> that inherits most setting from the old bug.
most setting -> "most settings"
> This makes you
+ to be able to track the same concerns for new releases on the
+ new bug easily.
-> This allows you to easily track similar concerns in a new bug.
"go to the old bug to clone" -> "go to the bug that you want to clone"
> This will take you to <quote>Enter Bug</quote>
s/you to/you to the/
Otherwise looks good. If I don't get to it, carry review forward on commited patch.
Attachment #246450 -
Flags: review?(documentation) → review+
Comment 4•18 years ago
|
||
Comment on attachment 246450 [details] [diff] [review]
docs patch for tip
Oh, actually, make the section title "Cloning Bugs".
Comment 5•18 years ago
|
||
Lots of lines got 2 more spaces as indentation, so diff sucks due to white-space-ing issues.
Attachment #246450 -
Attachment is obsolete: true
Attachment #247822 -
Flags: review+
Updated•18 years ago
|
Assignee: documentation → bmo2007
Comment 6•18 years ago
|
||
Tip:
Checking in webtools/bugzilla/docs/xml/using.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/using.xml,v <-- using.xml
new revision: 1.58; previous revision: 1.57
done
Checking in webtools/bugzilla-2_22/docs/xml/using.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/using.xml,v <-- using.xml
new revision: 1.37.2.15; previous revision: 1.37.2.14
done
Leaving bug open for 2.20 commit.
Status: NEW → ASSIGNED
Comment 8•18 years ago
|
||
2.20.3:
Checking in docs/xml/using.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/using.xml,v <-- using.xml
new revision: 1.33.2.18; previous revision: 1.33.2.17
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•