head	1.3;
access;
symbols
	dlr:1.1.1
	TIGRIS_0_9_2_4:1.1
	TIGRIS_0_9_2_3:1.1
	HELM_PEER_PORT_BRANCH:1.1.1.1
	TURBINE_PEER:1.1
	TIGRIS_0_9_2_1:1.1
	TIGRIS_0_9_2:1.1.0.6
	TIGRIS_0_8_4:1.1.0.4
	TIGRIS_0_9_0:1.1.0.2;
locks; strict;
comment	@# @;


1.3
date	2001.02.26.23.38.38;	author lori;	state dead;
branches;
next	1.2;

1.2
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.1;

1.1
date	2000.12.30.23.22.00;	author jrobbins;	state Exp;
branches
	1.1.1.1
	1.1.4.1
	1.1.8.1;
next	;

1.1.1.1
date	2001.02.21.00.31.52;	author dlr;	state Exp;
branches;
next	;

1.1.4.1
date	2001.01.16.00.17.44;	author susank;	state Exp;
branches;
next	;

1.1.8.1
date	2001.02.17.18.39.15;	author edk;	state Exp;
branches;
next	;


desc
@@


1.3
log
@removed file; obsoleted by 1.0 help
@
text
@<HTML>
<HEAD>

<TITLE>IssueZilla Issue Tracking</TITLE>

</HEAD>
<BODY>
<!-- style/format note: Headings/fonts should be updated to conform to scast style -->

<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>IssueZilla issue tracking</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText" VALIGN="top">

     <P>Issues are tasks and activities associated with development
     projects. These are tracked with IssueZilla, a variant of the
     BugZilla bug tracking system with several important
     differences. The most important distinction is that IssueZilla is
     more generalized to handle all kinds of <I>issues</I> -- not just
     code-based <I>bugs</I> -- in collaborative development
     projects. Issues are classified into several types:

      <UL>
       <LI>defects (a.k.a. "bugs")
       <LI>enhancements
       <LI>features
       <LI>tasks
       <LI>patches
      </UL>
<P>
(<A HREF="DomainDocsIssues_EnterModify.html#issue_type">See issue definitions for more information.</A>)

     <P>Another important difference is that you do not have to log in
     separately to IssueZilla. Each hosted project has its own unique
     issue database that project members have access to.

     <P>IssueZilla enables <I>any project member</I> to query, create,
     assign, and modify issues for specific project components. As a
     project member, you are also notified automatically by email
     whenever issues are assigned to you and whenever there is
     activity on issues affecting your work. Entering the tasks you're
     planning to work on as issues helps you track your work
     plan. Because everyone is clued in to each project member's area
     of work, you can avoid duplicating efforts and even help out or
     offer feedback to each other.

     <P>Using issue tracking effectively requires an understanding of
     the IssueZilla tool and a working knowledge of what constitutes a
     well-written issue report.

     <BLOCKQUOTE>
     <P><A HREF="DomainDocsIssues_GettingStarted.html">Getting started with IssueZilla</A>

     <P><A HREF="DomainDocsIssues_EnterModify.html">Entering and modifying issues</A>

     <P><A HREF="DomainDocsIssues_Query.html">Querying and tracking issues</A>

     <P><A HREF="DomainDocsIssues_Metrics.html">Issue metrics and reports</A>
     </BLOCKQUOTE>

     <P>Additional links for information about writing useful issue reports:

     <UL>
      <LI><A HREF="issue_lifecycle.html">The issue life cycle</A>
      <LI><A HREF="issuewritinghelp.html">Issue writing guidelines</A>
      <LI><A HREF="issuezilla_tipsandtricks.html">IssueZilla tips and tricks</A>
	  <LI><A HREF="contributing_patches.html">Contributing patches</A>	
      <LI><A HREF="http://www.trilobyte.net/barnsons/FAQ.html">BugZilla FAQ</A>**
      <LI><A HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html">Step-by-step help for bug entry</A>**
      <LI><A HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html">BugZilla guide to writing good bug reports</A>**
     </UL>

     <P><FONT SIZE="-1"><B><I>**</I></B> The BugZilla help
     documentation listed above offers useful bug-writing guidelines
     that are applicable to IssueZilla, however be aware that there
     are differences between the two tools. Parts of BugZilla
     documentation may not apply or may not address certain features
     in IssueZilla, and vice versa. Because IssueZilla is an open
     source derivative of BugZilla (version 2.11), it is still a work
     in progress. For those who are interested in more information
     about this, visit <a
     href="http://mozilla.org/bugs/">Mozilla.org</a>.</FONT>

     <P><FONT SIZE="-1"><B><I>A note about cookies</I></B>: Cookies
     are a prerequisite for creating an account and logging in to
     IssueZilla. If cookies are disabled on your system, you will at
     least need to enable the following cookies: "Issuezilla_login" or
     "Issuezilla_logincookie." Other than logging in, IssueZilla uses
     cookies to cache an issue's current version and for ordering the
     most recent query.cgi search during a session.</FONT>
    </TD>
  </TR>
</TABLE>
</BODY>
</HTML>
@


1.2
log
@added <title> tags to all files
@
text
@@


1.1
log
@moved core documentation into helm, fewer overrides need to be in instances now
@
text
@d1 7
d98 2
@


1.1.1.1
log
@Replacing the HEAD with the HELM_PEER_PORT_BRANCH.
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>IssueZilla Issue Tracking</TITLE>

</HEAD>
<BODY>
a90 2
</BODY>
</HTML>
@


1.1.8.1
log
@porting changes from the head to the branch
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>IssueZilla Issue Tracking</TITLE>

</HEAD>
<BODY>
a90 2
</BODY>
</HTML>
@


1.1.4.1
log
@adding the generic, default docs into this branch, bc they are in the head and nec for instantiations using stable branches
@
text
@@

