Source code for Issuezilla (CollabNet's enhancement of Bugzilla) is not 
currently publicly available. 

For your convenience, 
please find following the URL to Buzilla source code: 
http://www.mozilla.org/bugs/source.html

I have seen the code to issuezilla posted somewhere. Though I cannot 
find it any more. I still think that the source should be public, as this is an 
open source project, at the very least, the tools should be public too. Is 
there some reason why it cannot be open source? Other users of bugzilla 
that have modified their source have made it open (redhat, loki...) and 
some people choose to use it because of the benefits. As a bugzilla user 
myself, I would like to have the option of choosing the issue type for my 
installation and would like this available. Since I enjoy working on bugzilla 
and helping with that project, I would like to be able to contribute here 
when special cases come up that require more special features that help 
the openoffice community. I strongly urge you to reconsider this descision 
and to open the code.

fyi: the source to issuezilla is public; you can find it at

http://sandbox.tigris.org/source/browse/sandbox/issuezilla/

it can also be accessed via anonymous cvs.  the version which is in the head of
the cvs tree assumes that you're using this as part of helm & associated tools. 
all of those tools are public; but if you're interested in doing this, you'll
probably want to subscribe to dev@helm.tigris.org; if you want to look at the
version of IZ which is in use on openoffice.org, i think ISSUEZILLA_BASELINE may
be the tag you want.

if you have add'l questions or patches which you'd like to contribute, you're
welcome to join the mailing lists for these tools. ;-)

The source code for IssueZilla is publically available via CVS on tigris.org,
as is the rest of the tigris project. Because we believe in 
open-source, of course IssueZilla has been publicly available since it was
first setup on openoffice.org. See
http://www.openoffice.org/www-discuss/current/msg00526.html which
has a link to the IssueZilla patch residing at
http://www.openoffice.org/issues/show_bug.cgi?id=18

IssueZilla is part of the tigris open-source hosting project
The sources for tigris (aka SourceCast) are all checked
in to CVS.  However, the version of IssueZilla on the "TRUNK"
will certainly not run standalone, and is a much greater departure 
from Bugzilla than IssueZilla currently used by openoffice.org. For example,
SourceCast's IssueZilla features support for authentication and access control
for private or close-sourced projects, as well as open-source ones. SourceCast's
IssueZilla also features integrated authentication, allowing the same login/
password to be used for web-administration, CVS, and issue-tracking.

If you want the more easy-to-integrate and closer to "standard" Bugzilla
version of IssueZilla, (the version used for OpenOffice.org)... that
version  has been tagged in CVS. You may access it as :

cvs -d ':pserver:guest@cvs.tigris.org:/cvs' login
	(password guest)
cvs -d ':pserver:guest@cvs.tigris.org:/cvs' co -r ISSUEZILLA_OPENOFFICE
\ 	                                                sandbox/issuezilla

To retrieve SourceCast (and it's integrated and much-changed issuezilla)

cd /usr/local/
cvs -d :pserver:guest@cvs.tigris.org:/cvs login
	(password: guest)
cvs -d :pserver:guest@cvs.tigris.org:/cvs co sandbox
cd sandbox
cvs -d :pserver:guest@cvs.tigris.org:/cvs co anzu eyebrowse helm joist
ln -s /usr/local/sandbox /usr/local/tigris

(And for further information on the various components checked out above:
helm-dev-subscribe@tigris.org  -- java admin interface and tool integration
joist-dev-subscribe@tigris.org -- java platform
eyebrowse-dev-subscribe...     -- servlet based mail archiver
anzu-dev-subscribe...          -- java-based intfc to ezmlm/qmail/nntp
)

For more info, see the associated websites helm.tigris.org, joist.tigris.org
eyebrowse.tigris.org, anzu.tigris.org, etc....

There, that should be enough to get you started. :-)

PS: please check out scarab.tigris.org, or upcoming issuezilla replacement...

mine

duplicate issue

*** This issue has been marked as a duplicate of 18 ***

verified

*** Issue 271 has been marked as a duplicate of this issue. ***

As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.