summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjocuri%softhome.net <>2003-11-01 18:51:41 +0100
committerjocuri%softhome.net <>2003-11-01 18:51:41 +0100
commit6d07621d169d588832706c946a058d037e810edc (patch)
tree27b372ccf28aaf11dc51bbd07620c8857a591980
parentaba0ad551fab3f31935efa77073b8e6a9c6212de (diff)
downloadbugzilla-6d07621d169d588832706c946a058d037e810edc.tar.gz
bugzilla-6d07621d169d588832706c946a058d037e810edc.tar.xz
Bug 123565: Add to FAQ: Why can't I close bugs from "Change Several Bugs at Once" ?; r=justdave; a=justdave.
-rw-r--r--docs/xml/faq.xml23
1 files changed, 23 insertions, 0 deletions
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">