From: jocuri%softhome.net <>
Date: Sat, 1 Nov 2003 18:12:12 +0000 (+0000)
Subject: Bug 123565: Add to FAQ: Why can't I close bugs from "Change Several Bugs at Once... 
X-Git-Tag: bugzilla-2.16.4~9
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6403337d9a29e0bedbadaa2b9f6202e77347078a;p=thirdparty%2Fbugzilla.git

Bug 123565: Add to FAQ: Why can't I close bugs from "Change Several Bugs at Once" ?; r=justdave; a=justdave.
---

diff --git a/docs/xml/faq.xml b/docs/xml/faq.xml
index de635a2dc5..917f5ef810 100644
--- a/docs/xml/faq.xml
+++ b/docs/xml/faq.xml
@@ -1141,6 +1141,29 @@
 	</answer>
       </qandaentry>
 
+      <qandaentry>
+    <question id="faq-use-close">
+      <para>
+        Why can't I close bugs from the "Change Several Bugs at Once" page?
+      </para>
+    </question>
+    <answer>
+      <para>
+        The logic flow currently used is RESOLVED, then VERIFIED, then CLOSED.
+        You <emphasis>can</emphasis> mass-CLOSE bugs from the change several
+        bugs at once page. <emphasis>but</emphasis>, every bug listed on the
+        page has to be in VERIFIED state before the control to do it will show
+        up on the form. You can also mass-VERIFY, but every bug listed has to be
+        RESOLVED in order for the control to show up on the form. The logic
+        behind this is that if you pick one of the bugs that's not VERIFIED and
+        try to CLOSE it, the bug change will fail miserably (thus killing any
+        changes in the list after it while doing the bulk change) so it doesn't
+        even give you the choice.
+      </para>
+    </answer>
+      </qandaentry>
+
+
     </qandadiv>
 
     <qandadiv id="faq-hacking">