# Provides a silly 'back-door' mechanism to let me automatically insert
! # issues from the netscape issuesystem. Other installations of Issuezilla probably
# don't need to worry about this file any.
use diagnostics;
***************
*** 79,92 ****
sub Punt {
my ($label, $value) = (@_);
my $maintainer = Param("maintainer");
! print "I don't know how to move into Bugzilla a bug with a $label of $value.
If you really do need to do this, speak to $maintainer and maybe he
can teach me.";
exit;
}
! # Do remapping of things from BugSplat world to Bugzilla.
if ($prod eq "Communicator") {
$prod = "Browser";
--- 79,92 ----
sub Punt {
my ($label, $value) = (@_);
my $maintainer = Param("maintainer");
! print "I don't know how to move into Issuezilla an issue with a $label of $value.
If you really do need to do this, speak to $maintainer and maybe he
can teach me.";
exit;
}
! # Do remapping of things from IssueSplat world to Issuezilla.
if ($prod eq "Communicator") {
$prod = "Browser";
***************
*** 121,130 ****
my $longdesc =
! "(This bug imported from BugSplat, Netscape's internal bugsystem. It
! was known there as bug #$::FORM{'bug_id'}
! http://scopus.netscape.com/bugsplat/show_bug.cgi?id=$::FORM{'bug_id'}
! Imported into Bugzilla on " . time2str("%D %H:%M", time()) . ")
" . $::FORM{'long_desc'};
--- 121,130 ----
my $longdesc =
! "(This issue imported from IssueSplat, Netscape's internal issuesystem. It
! was known there as issue #$::FORM{'issue_id'}
! http://scopus.netscape.com/issuesplat/show_bug.cgi?id=$::FORM{'issue_id'}
! Imported into Issuezilla on " . time2str("%D %H:%M", time()) . ")
" . $::FORM{'long_desc'};
***************
*** 142,157 ****
my @list = ('reporter', 'assigned_to', 'product', 'version', 'rep_platform',
! 'op_sys', 'bug_status', 'bug_severity', 'priority', 'component',
'short_desc', 'creation_ts', 'delta_ts',
! 'bug_file_loc', 'qa_contact', 'groupset');
my @vallist;
foreach my $i (@list) {
push @vallist, SqlQuote($::FORM{$i});
}
! my $query = "insert into bugs (" .
join(',', @list) .
") values (" .
join(',', @vallist) .
--- 142,157 ----
my @list = ('reporter', 'assigned_to', 'product', 'version', 'rep_platform',
! 'op_sys', 'issue_status', 'issue_type', 'priority', 'component',
'short_desc', 'creation_ts', 'delta_ts',
! 'issue_file_loc', 'qa_contact', 'groupset');
my @vallist;
foreach my $i (@list) {
push @vallist, SqlQuote($::FORM{$i});
}
! my $query = "insert into issues (" .
join(',', @list) .
") values (" .
join(',', @vallist) .
***************
*** 163,178 ****
SendSQL("select LAST_INSERT_ID()");
my $zillaid = FetchOneColumn();
! SendSQL("INSERT INTO longdescs (bug_id, who, bug_when, thetext) VALUES " .
"($zillaid, $::FORM{'reporter'}, now(), " . SqlQuote($longdesc) . ")");
foreach my $cc (split(/,/, $::FORM{'cc'})) {
if ($cc ne "") {
my $cid = DBNameToIdAndCheck("$cc\@netscape.com", 1);
! SendSQL("insert into cc (bug_id, who) values ($zillaid, $cid)");
}
}
! print "Created bugzilla bug $zillaid\n";
system("./processmail", $zillaid);
--- 163,178 ----
SendSQL("select LAST_INSERT_ID()");
my $zillaid = FetchOneColumn();
! SendSQL("INSERT INTO longdescs (issue_id, who, issue_when, thetext) VALUES " .
"($zillaid, $::FORM{'reporter'}, now(), " . SqlQuote($longdesc) . ")");
foreach my $cc (split(/,/, $::FORM{'cc'})) {
if ($cc ne "") {
my $cid = DBNameToIdAndCheck("$cc\@netscape.com", 1);
! SendSQL("insert into cc (issue_id, who) values ($zillaid, $cid)");
}
}
! print "Created issuezilla issue $zillaid\n";
system("./processmail", $zillaid);
Index: booleanchart.html
===================================================================
RCS file: /cvsroot/mozilla/webtools/bugzilla/booleanchart.html,v
retrieving revision 1.3
diff -c -r1.3 booleanchart.html
*** booleanchart.html 2000/08/16 23:07:37 1.3
--- booleanchart.html 2000/09/29 04:57:12
***************
*** 10,16 ****
! The Bugzilla query page is designed to be reasonably easy to use.
But, with such ease of use always comes some lack of power. The
"boolean chart" section is designed to let you do very powerful
queries, but it's not the easiest thing to learn (or explain).
--- 10,16 ----
! The Issuezilla query page is designed to be reasonably easy to use.
But, with such ease of use always comes some lack of power. The
"boolean chart" section is designed to let you do very powerful
queries, but it's not the easiest thing to learn (or explain).
***************
*** 48,54 ****
The most subtle thing is this "Add another boolean chart" button.
This is almost the same thing as the "And" button. The difference is
if you use one of the fields where several items can be associated
! with a single bug. This includes "Comments", "CC", and all the
"changed [something]" entries. Now, if you have multiple terms that
all talk about one of these fields, it's ambiguous whether they are
allowed to be talking about different instances of that field. So,
--- 48,54 ----
The most subtle thing is this "Add another boolean chart" button.
This is almost the same thing as the "And" button. The difference is
if you use one of the fields where several items can be associated
! with a single issue. This includes "Comments", "CC", and all the
"changed [something]" entries. Now, if you have multiple terms that
all talk about one of these fields, it's ambiguous whether they are
allowed to be talking about different instances of that field. So,
***************
*** 58,66 ****
For example: if you search for "priority changed to P5" and
! "priority changed by person@addr", it will only find bugs where the
given person at some time changed the priority to P5. However, if
! what you really want is to find all bugs where the milestone was
changed at some time by the person, and someone (possibly someone
else) at some time changed the milestone to P5, then you would put
the two terms in two different charts.
--- 58,66 ----
For example: if you search for "priority changed to P5" and
! "priority changed by person@addr", it will only find issues where the
given person at some time changed the priority to P5. However, if
! what you really want is to find all issues where the milestone was
changed at some time by the person, and someone (possibly someone
else) at some time changed the milestone to P5, then you would put
the two terms in two different charts.
***************
*** 74,79 ****
! Last modified: Wed Aug 16 16:06:36 2000