From 6d07621d169d588832706c946a058d037e810edc Mon Sep 17 00:00:00 2001
From: "jocuri%softhome.net" <>
Date: Sat, 1 Nov 2003 17:51:41 +0000
Subject: Bug 123565: Add to FAQ: Why can't I close bugs from "Change Several
 Bugs at Once" ?; r=justdave; a=justdave.

---
 docs/xml/faq.xml | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

(limited to 'docs')

diff --git a/docs/xml/faq.xml b/docs/xml/faq.xml
index 548eb8172..e2cebd647 100644
--- a/docs/xml/faq.xml
+++ b/docs/xml/faq.xml
@@ -1130,6 +1130,29 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
 	</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">
-- 
cgit v1.2.3-24-g4f1b