355302 - Documentation for the "clone bug" feature

Status: RESOLVED FIXED

(Bugzilla :: Documentation, enhancement)

Description

[Daryl Mullins]

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

[Max Kanat-Alexander]

That's true--there's lots of features that don't have documentation. We could use some volunteer assistance there! :-)

Comment 2

[victory <[e-mail]>]

Attachment: docs patch for tip

Comment 3

[Vlad Dascalu]

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.

Comment 4

[Vlad Dascalu]

Comment on attachment 246450 [details] [diff] [review]
docs patch for tip

Oh, actually, make the section title "Cloning Bugs".

Comment 5

[Vlad Dascalu]

Attachment: docs patch for tip, nits fixed (carrying review+)

Lots of lines got 2 more spaces as indentation, so diff sucks due to white-space-ing issues.

Comment 6

[Vlad Dascalu]

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.

Comment 7

[Vlad Dascalu]

Attachment: docs patch for 2-20, nits fixed (carrying review+)

Patch for 2-20.

Comment 8

[Frédéric Buclin]

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