head	1.13;
access;
symbols
	TIGRIS_1_1_0RC2:1.7.6.1
	TIGRIS_1_1_0RC1:1.7.6.1
	TIGRIS_1_1:1.7.6.1.0.2
	TIGRIS_1_0_8:1.7.6.1
	TIGRIS_1_0_8RC3:1.7.6.1
	TIGRIS_1_0_8RC2:1.7.6.1
	TIGRIS_1_0_8RC1:1.7.6.1
	TIGRIS_1_0_7:1.7.6.1
	TIGRIS_1_0_7RC3:1.7.6.1
	TIGRIS_1_0_7RC2:1.7.6.1
	TIGRIS_1_0_7RC1:1.7.6.1
	TIGRIS_1_0_6:1.7.6.1
	TIGRIS_1_0_6RC5:1.7.6.1
	TIGRIS_1_0_6RC4:1.7.6.1
	TIGRIS_1_0_6RC3:1.7
	TIGRIS_1_0_6RC2:1.7
	TIGRIS_1_0_6RC1:1.7
	TIGRIS_1_0_5:1.7
	TIGRIS_1_0_5RC6:1.7
	TIGRIS_1_0_5RC5:1.7
	TIGRIS_1_0_5RC4:1.7
	TIGRIS_1_0_5RC3:1.7
	TIGRIS_1_0_5RC2:1.7
	TIGRIS_1_0_5RC1:1.7
	TIGRIS_1_0_4:1.7
	TIGRIS_1_0_3:1.7
	TIGRIS_1_0_2:1.7
	TIGRIS_1_0_1:1.7
	TIGRIS_1_0:1.7.0.6
	TIGRIS_1_0_0:1.7
	TIGRIS_1_0_0_RC1:1.7.0.2;
locks; strict;
comment	@# @;


1.13
date	2001.08.23.23.04.06;	author tberry;	state Exp;
branches;
next	1.12;

1.12
date	2001.08.23.23.02.41;	author tberry;	state Exp;
branches;
next	1.11;

1.11
date	2001.07.26.22.46.07;	author tberry;	state Exp;
branches;
next	1.10;

1.10
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.9;

1.9
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.8;

1.8
date	2001.06.04.21.04.10;	author lori;	state Exp;
branches;
next	1.7;

1.7
date	2001.03.12.23.31.49;	author lori;	state Exp;
branches
	1.7.6.1;
next	1.6;

1.6
date	2001.03.10.01.30.19;	author tberry;	state Exp;
branches;
next	1.5;

1.5
date	2001.02.15.21.15.21;	author lori;	state Exp;
branches;
next	1.4;

1.4
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.3;

1.3
date	2001.02.09.00.59.20;	author susank;	state Exp;
branches;
next	1.2;

1.2
date	2001.02.05.16.35.54;	author lori;	state Exp;
branches;
next	1.1;

1.1
date	2001.01.29.19.46.27;	author lori;	state Exp;
branches;
next	;

1.7.6.1
date	2001.06.13.00.33.40;	author lori;	state Exp;
branches;
next	;


desc
@@


1.13
log
@fixed minor issue with index.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@  <div class="docs" id="projectissues">
   <h2>Project Issues</h2>

   <div class="toc">
    <h3>Project resources for members: Index</h3>

    <ul>
     <li>
      <a href="ProjectMemberResources.html">Project resources for members</a> 

        <ul> <li>
     <a href="Learning.html">Learning about projects</a> </li>
          <li><a href="ProjectHome.html">Project Home Page</a></li>
          <li><a href="ProjectNews.html">Project News</a></li>
          <li><a href="ProjectMemberList.html">Project Members</a></li>
          <li><a href="ProjectMail.html">Project Mailing Lists</a></li>
          <li><a href="ProjectDocuments.html">Project Documents</a></li>
          <li><a href="ProjectSource.html">Project Source Code</a></li>
          <li> <strong>You are here:</strong> Project Issues 
            <ul>
              <li><a href="#accessissues">Accessing project issues</a></li>
              <li><a href="#aboutIZ">About the IssueZilla tool</a></li>
              <li><a href="#useraccounts">Setting your issue tracking user preferences</a></li>
              <li><a href="#permissions">About your issue tracking permissions</a></li>
            </ul>
          </li>
        </ul>
     </li><li><a href="hostedtools.html">Hosted tools</a></li>
      <li><a href="ProjectAdd.html">Creating a new project</a></li>
    </ul>
   

   <h3>More help on issue tracking</h3>

   <ul>
    <li><a href="ddIssues_EnterModify.html">Entering and modifying issues</a></li>

    <li><a href="ddIssues_Query.html">Querying and tracking issues</a></li>

    <li><a href="ddIssues_Reports.html">Generating status reports about project issues</a></li>

    <li><a href="#Moreinfo">More how-to information about issues and issue tracking</a></li>
   </ul></div>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>

   <h3><a id="accessissues" name="accessissues">Accessing project issues</a></h3>

   <p>All development activities for each project hosted on this site are tracked in a unique database. The <strong>Issue Tracking</strong> link in the Project Resources toolbar displays the <b>Project Issues</b> page, the entry point to that project's issue database. Issue tracking provides the following benefits:</p>

   <ol>
    <li>Ability to chart the progress of individuals and the overall project</li>

    <li>Tracking and maintainance of project history</li>

    <li>Generation and reporting of ongoing to-do lists for all project members.</li>
   </ol>

   <p>The different sections appearing in the <b>Project Issues</b> page indicate the following issue tracking options available to you:</p>

   <dl>
    <dt><a href="ddIssues_Query.html"><b>Query Database of Issues</b></a></dt>

    <dd>Search project issues by number, keywords, assignee, or other criteria.</dd>

    <dt><a href="ddIssues_EnterModify.html"><b>Enter An Issue</b></a></dt>

    <dd>Write and commit an issue report to the database.</dd>

    <dt><a href="ddIssues_Query.html#trackissue"><b>My Issues</b></a></dt>

    <dd>View a list of project issues assigned to you.</dd>

    <dt><a href="#useraccounts"><b>My Preferences</b></a></dt>

    <dd>Configure your issue tracker user settings.</dd>
   </dl>

   <h3><a id="aboutIZ" name="aboutIZ">About IssueZilla</a></h3>

   <p>IssueZilla is the issue tracking tool used on this site. While it is a variant of BugZilla -- a bug tracking system you may already be familiar with -- IssueZilla is a more generalized tool for tracking many different kinds of activities in collaborative development projects. Additionally, IssueZilla does not require a separate login as BugZilla does. IssueZilla classifies issues into several types:</p>

   <ul>
    <li>Defects (a.k.a. "bugs")</li>

    <li>Enhancements</li>

    <li>Features</li>

    <li>Tasks</li>

    <li>Patches</li>
   </ul>

   <p>Each hosted project on this site has it's own, unique issues database. For open source projects in IssueZilla, all registered users may query, view, and report issues, while proprietary projects limit access to project members.</p>

   <p>Project members have additional permissions within IssueZilla to modify and reassign issues, as well as generate reports. Project members are also notified automatically by email whenever issues are assigned to them or there is activity on issues affecting their work.</p>

   <p>Entering the tasks you're planning to work on as issues helps you devise and follow a work plan. Because everyone is aware of each project member's area of work, you can avoid duplicating efforts and even help out or offer feedback to other project members. Effective issue tracking requires an understanding of the IssueZilla tool and a working knowledge of what constitutes a well-written issue report.</p>

   <h3><a id="useraccounts" name="useraccounts">Setting your issue tracking user preferences</a></h3>

   <p>When you join a hosted development project on this site, you automatically get an IssueZilla account for access to that project's issues.</p>

   <p>Information about your account is available either by clicking the <strong>My Preferences</strong> link on the <b>Project Issues</b> page. Once you have entered the issue tracking area of the site you can click on the <strong>Edit prefs</strong> link in the Issue Tracking toolbar, which appears in all issue tracking screens. You have several options to change your user settings:</p>

   <dl>
    <dt>Email settings</dt>

    <dd>Controls your automatic email notification settings.</dd>

    <dt>Page footer</dt>

    <dd>Include/exclude "My issues" or your named, custom queries in every IssueZilla page footer.</dd>

    <dt>Permissions</dt>

    <dd>Displays your issue tracking permissions but cannot be changed because permissions are assigned by the Project Owner. (See next section.)</dd>
   </dl>

   <h3><a id="permissions" name="permissions">About issue tracking permissions</a></h3>

   <p>Once a user becomes a member of a project, he or she is granted additional IssueZilla permissions beyond the default database query capabilities. Permissions can be viewed by clicking on the <strong>My Preferences</strong> link on the <b>Project Issues</b> page, or the <strong>Edit Prefs</strong> link in the Issue Tracking toolbar.</p>

   <p>Issue tracking permissions depend upon project role:</p>

   <ul>
    <li>Observers can create and modify issues, but can make changes to only their own issues. Observers have the ability to comment on any issue.</li>

    <li>Developers (code or content) can report and modify their own and other project issues. If they have been granted the "Can edit all aspects of any issue" permission, they have the ability to alter all issue characteristics, including milestones and issue assignments.</li>

    <li>Project initiators automatically are granted administrative level IssueZilla permissions with additional rights to configure issue tracking for the project. Project initiators can also assign IssueZilla-specific permissions to other project members.</li>
   </ul>

   <p>Additional permissions can be requested through the project owner. You may need to request a new project role.</p>

   <p>Permissions affect the lifecycle and resolution of issues. For example, if you have the "Can confirm an issue" permission, then you can change the status of any <b>UNCONFIRMED</b> issue to <b>NEW</b> . A change in issue status sends an alert to the owner and all other project members associated with the issue.To understand more about issue status, read more about the <a href="issue_lifecycle.html">lifecycle of issues</a>.</p>

   <h3><a id="Moreinfo" name="Moreinfo">More resources about issues and issue tracking</a></h3>

   <ul>
    <li><a href="issue_lifecycle.html">The issue life cycle</a></li>

    <li><a href="issuewritinghelp.html">Issue writing guidelines</a></li>

    <li><a href="issuezilla_tipsandtricks.html">IssueZilla tips and tricks</a></li>

    <li><a href="contributing_patches.html">Contributing patches</a></li>

    <li><a href="http://www.trilobyte.net/barnsons/FAQ.html">BugZilla FAQ</a>**</li>

    <li><a href="http://www.mozilla.org/quality/help/bugzilla-helper.html">Step-by-step help for bug entry</a>**</li>

    <li><a href="http://www.mozilla.org/quality/bug-writing-guidelines.html">BugZilla guide to writing good bug reports</a>**</li>

    <li><a href="http://scarab.tigris.org">Scarab</a>, an open source issue tracking development project</li>
   </ul>

   <p><b><i>**</i></b> These links listed are associated with BugZilla, but offer useful bug-writing guidelines that are applicable to IssueZilla. 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>.</p>

   <p>If you are interested in finding out about other bug tracking systems being developed, see the <a href="http://scarab.tigris.org">scarab</a> open source project.</p>

   <p><b><i>A note about IssueZilla and 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 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.</p>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.12
log
@added index info.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d31 1
a31 1
   </div>
d43 1
a43 1
   </ul>
@


1.11
log
@removed link to ProjectDownload.  This feature no longer exists.

Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d11 2
a12 1
        <ul>
d28 2
a29 1
     </li>
@


1.10
log
@html usage revision
@
text
@a10 18
      <ul>
       <li><a href="ProjectHome.html">Project Home Page</a></li>

       <li><a href="ProjectNews.html">Project News</a></li>

       <li><a href="ProjectDownload.html">Project Files</a></li>

       <li><a href="ProjectMemberList.html">Project Members</a></li>

       <li><a href="ProjectMail.html">Project Mailing Lists</a></li>

       <li><a href="ProjectDocuments.html">Project Documents</a></li>

       <li><a href="ProjectSource.html">Project Source Code</a></li>

       <li>
        <strong>You are here:</strong> Project Issues

d12 14
a25 7
         <li><b><a href="#accessissues">Accessing project issues</a></b></li>

         <li><a href="#aboutIZ">About the IssueZilla tool</a></li>

         <li><a href="#useraccounts">Setting your issue tracking user preferences</a></li>

         <li><a href="#permissions">About your issue tracking permissions</a></li>
a26 2
       </li>
      </ul>
@


1.9
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 16
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Project Resources for Project Members</title>
<style type="text/css">
 dt.c4 {font-weight: bold}
 li.c3 {list-style: none}
 p.c2 {font-weight: bold}
 div.c1 {margin-left: 2em}
</style>
 </head>

 <body>
 <div class="docs" id="docid">
<h2>Project Issues</h2>
d4 2
a5 1
  <p><strong>Project resources for project members: Index</strong></p>
d7 6
a12 3
  <div>
   <dl>
    <dt><a href="ProjectMemberResources.html">Project resources for members</a></dt>
d14 1
a14 1
    <dd><a href="ProjectHome.html">Project Home Page</a></dd>
d16 1
a16 1
    <dd><a href="ProjectNews.html">Project News</a></dd>
d18 1
a18 1
    <dd><a href="ProjectDownload.html">Project Download</a></dd>
d20 1
a20 1
    <dd><a href="ProjectMemberList.html">Project Members</a></dd>
d22 1
a22 1
    <dd><a href="ProjectMail.html">Project Mailing Lists</a></dd>
d24 1
a24 1
    <dd><a href="ProjectDocuments.html">Project Documentation</a></dd>
d26 2
a27 1
    <dd><a href="ProjectSource.html">Project Source Code</a></dd>
d29 2
a30 2
    <dd>
     <b>You are here: Project Issues</b>
d32 1
a32 2
     <ul>
      <li><b><a href="#accessissues">Accessing project issues</a></b></li>
d34 1
a34 1
      <li><a href="#aboutIZ">About the IssueZilla tool</a></li>
d36 7
a42 1
      <li><a href="#useraccounts">Setting your issue tracking user preferences</a></li>
d44 1
a44 3
      <li><a href="#permissions">About your issue tracking permissions</a></li>
     </ul>
    </dd>
d46 2
a47 3
    <dt><a href="/servlets/HelpTOC">Back to main Help index</a></dt>
   </dl>
  </div>
d49 1
a49 1
  <p class="c2">More help on issue tracking</p>
d51 1
a51 3
  <div>
   <dl>
    <dt><a href="ddIssues_EnterModify.html">Entering and modifying issues</a></dt>
d53 2
a54 1
    <dt><a href="ddIssues_Query.html">Querying and tracking issues</a></dt>
d56 3
a58 1
    <dt><a href="ddIssues_Reports.html">Generating status reports about project issues</a></dt>
d60 1
a60 5
    <dt><a href="#Moreinfo">More how-to information about issues and issue tracking</a></dt>
   </dl>
  </div>
  
  <h3><a id="accessissues" name="accessissues">Accessing project issues</a></h3> 
d62 1
a62 1
  <p>All development activities for each project hosted on this site are tracked in a unique database. The <strong>Issue Tracking</strong> link in the Project Resources toolbar displays the <b>Project Issues</b> page, the entry point to that project's issue database. Issue tracking provides the following benefits:&#160;</p>
d64 2
a65 2
  <ol>
   <li>Ability to chart&#160;the progress of individuals and the overall project</li>
d67 1
a67 1
   <li>Tracking and maintainance&#160;of project history</li>
d69 2
a70 2
   <li>Generation and reporting of&#160;ongoing to-do lists for all project members.</li>
  </ol>
d72 1
a72 1
  <p>The different sections appearing in the <b>Project Issues</b> page indicate the following issue tracking options available to you:</p>
a73 1
  <blockquote>
a90 3
  </blockquote>
  
  <h3><a id="aboutIZ" name="aboutIZ">About IssueZilla</a></h3> 
d92 1
a92 1
  <p>IssueZilla is the issue tracking tool used on this site.&#160; While it is a variant of BugZilla -- a bug tracking system you may already be familiar with-- IssueZilla is a more generalized tool for tracking many different kinds of activities in collaborative development projects. Additionally, IssueZilla does not require a separate login as BugZilla does.&#160; IssueZilla classifies issues into several types:</p>
d94 1
a94 2
  <ul>
   <li class="c3"><a href="ddIssues_EnterModify.html#issue_type"></a></li>
d96 2
a97 1
   <li>Defects (a.k.a. "bugs")</li>
d99 1
a99 1
   <li>Enhancements</li>
d101 1
a101 1
   <li>Features</li>
d103 1
a103 1
   <li>Tasks</li>
d105 2
a106 2
   <li>Patches</li>
  </ul>
d108 1
a108 1
  <p>Each hosted project on this site has it's own, unique issues database. For open source projects in IssueZilla, all registered users may query, view, and report issues, while proprietary projects limit access to project members.</p>
d110 1
a110 1
  <p>Project members have additional permissions within IssueZilla to modify and reassign issues, as well as generate reports. Project members are also notified automatically by email whenever issues are assigned to them or&#160;there is activity on issues affecting&#160;their work.</p>
d112 1
a112 1
  <p>Entering the tasks you're planning to work on as issues helps you devise and follow a work plan. Because everyone is aware&#160;of each project member's area of work, you can avoid duplicating efforts and even help out or offer feedback to other project members. Effective issue tracking requires an understanding of the IssueZilla tool and a working knowledge of what constitutes a well-written issue report.</p>
d114 1
a114 3
  
  
  <h3><a id="useraccounts" name="useraccounts">Setting your issue tracking user preferences</a></h3>
d116 1
a116 1
  
d118 1
a118 1
  <p>When you join a hosted development project on this site, you automatically get an IssueZilla account for access to that project's issues.</p>
d120 2
a121 1
  <p>Information about your account is available either by clicking the <strong>My Preferences</strong> link on the <b>Project Issues</b> page.&#160; Once you have entered the issue tracking area of the site you can&#160;click on the <strong>Edit prefs</strong> link in the Issue Tracking toolbar, which appears in all issue tracking screens. You have several options to change your user settings:</p>
d123 1
a123 1
  
d125 1
a125 2
  <dl>
   <dt class="c4">Email settings</dt>
d127 1
a127 1
   <dd>Controls your automatic email notification settings.</dd>
d129 1
a129 1
   <dt class="c4">Page footer</dt>
d131 2
a132 1
   <dd>Include/exclude "My issues" or your named, custom queries in every IssueZilla page footer.</dd>
d134 1
a134 1
   <dt class="c4">Permissions</dt>
d136 1
a136 4
   <dd>Displays your issue tracking permissions but cannot be changed because permissions are assigned by the Project Owner. (See next section.)</dd>
  </dl>
  
  <h3><a id="permissions" name="permissions">About issue tracking permissions</a> </h3>
d138 1
a138 1
  <p>Once a user&#160;becomes a member of a project, he&#160;or she&#160;is granted additional IssueZilla permissions beyond the default database query capabilities. Permissions can be viewed by&#160;clicking on the&#160; <strong>My Preferences</strong> link on the <b>Project Issues</b> page, or the <strong>Edit Prefs</strong> link in the Issue Tracking toolbar.</p>
d140 2
a141 1
  <p>Issue tracking permissions depend upon project role:&#160;</p>
d143 1
a143 2
  <ul>
   <li>Observers can&#160;create and modify issues, but&#160;can make changes to&#160;only their own issues. Observers have the ability to comment on any issue.&#160;</li>
d145 2
a146 1
   <li>Developers&#160;(code or content) can report and modify&#160;their own and other project&#160; issues. If they have been granted&#160;the "Can edit all aspects of any issue" permission, they have the ability to alter all issue characteristics, including milestones and issue assignments.</li>
d148 1
a148 2
   <li>Project initiators automatically are granted&#160;administrative level IssueZilla&#160; permissions&#160;with additional&#160;rights to configure issue tracking for the&#160;project.&#160;Project initiators can also assign IssueZilla-specific permissions to other project members.</li>
  </ul>
d150 1
a150 1
  <p>Additional permissions can be requested through the project owner.&#160;You may need to request a new project role.</p>
d152 1
a152 1
  <p>Permissions affect the&#160;lifecycle and resolution of issues. For example, if you have the "Can confirm an issue" permission, then you can change the status of any <b>UNCONFIRMED</b> issue to <b>NEW</b> . A change in issue status sends an alert to the owner and all other project members associated with the issue.To understand more about issue status, read more about the <a href="issue_lifecycle.html">lifecycle of issues</a>.</p>
d154 2
a155 3
  
  
  <h3><a id="Moreinfo" name="Moreinfo">More resources about issues and issue tracking</a></h3> 
d157 1
a157 2
  <ul>
   <li><a href="issue_lifecycle.html">The issue life cycle</a></li>
d159 1
a159 1
   <li><a href="issuewritinghelp.html">Issue writing guidelines</a></li>
d161 1
a161 1
   <li><a href="issuezilla_tipsandtricks.html">IssueZilla tips and tricks</a></li>
d163 1
a163 1
   <li><a href="contributing_patches.html">Contributing patches</a></li>
d165 1
a165 1
   <li><a href="http://www.trilobyte.net/barnsons/FAQ.html">BugZilla FAQ</a>**</li>
d167 1
a167 1
   <li><a href="http://www.mozilla.org/quality/help/bugzilla-helper.html">Step-by-step help for bug entry</a>**</li>
d169 2
a170 1
   <li><a href="http://www.mozilla.org/quality/bug-writing-guidelines.html">BugZilla guide to writing good bug reports</a>**</li>
d172 1
a172 2
   <li><a href="http://scarab.tigris.org">Scarab</a>, an open source issue tracking development project</li>
  </ul>
d174 1
a174 1
  <p><b><i>**</i></b> These links listed are associated with BugZilla, but offer useful bug-writing guidelines that are applicable to IssueZilla. 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>.</p>
d176 1
a176 1
  <p>If you are interested in finding out about other bug tracking systems being developed, see the <a href="http://scarab.tigris.org">scarab</a> open source project.</p>
d178 5
a182 7
  <p><b><i>A note about IssueZilla and 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 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.</p>

  
  
<div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div> </div>
</body>
</html>
@


1.8
log
@fixed broken index link to Project Members help doc; issue 4348
@
text
@d1 2
d4 9
a12 1
<head>
d14 3
a16 1
<title>Project Resources for Project Members</title>
d18 22
a39 147
</head>
<body>
   
<p>
<span class=header>Project Issues</span>
<p>
<span class="PlainText"><strong>Project resources for project members: Index 
    </strong> 
         
    
<p>
<ul>
	<dl>
       	<dt><a href="ProjectMemberResources.html">Project resources for members</a></a>
        <dd><a href="ProjectHome.html">Project Home Page</a>
        <dd><a href="ProjectNews.html">Project News</a>
        <dd><a href="ProjectDownload.html">Project Download</a>
	<dd><a href="ProjectMemberList.html">Project Members</a>
        <dd><a href="ProjectMail.html">Project Mailing Lists</a>
	<dd><a href="ProjectDocuments.html">Project Documentation</a>
        <dd><a href="ProjectSource.html">Project Source Code</a>
        <dd><b>You are here: Project Issues
			<ul>
				<li><a href="#accessissues">Accessing project issues
				<li><a href="#aboutIZ">About the IssueZilla tool</a>
    			<li><a href="#useraccounts">Setting your issue tracking user preferences</a>
     			<li><a href="#permissions">About your issue tracking permissions</a></li>
			</ul></b>
	<dt><a href="/servlets/HelpTOC">Back to main Help index</a></dt>
	</dl>
</ul>

<p>
<b>More help on issue tracking</b>
<ul>
	<dl>
	<dt><a href="ddIssues_EnterModify.html">Entering and modifying issues</a>
	<dt><a href="ddIssues_Query.html">Querying and tracking issues</a>
	<dt><a href="ddIssues_Reports.html">Generating status reports about project issues</a>
	<dt><a href="#Moreinfo">More how-to information about issues and issue tracking</a>
	</dl>
</ul>

<p>
<hr noshade size=1>
<a name="accessissues"></a><span class="InputHeader">Accessing project issues</span>
<p>
All development activities for each project hosted on 
    this site are tracked in a unique database. 
The <strong>Issue Tracking </strong>  link in the Project Resources toolbar displays the <b>Project Issues</b>           
          page, the entry point to that project's 
    issue database. Issue tracking provides the following benefits:&nbsp;
    <ol><p><li> Ability to chart&nbsp;the progress of individuals and the overall project
    
    
      <li>Tracking and maintainance&nbsp;of project history
      <li>Generation and reporting of&nbsp;ongoing to-do lists for all project 
    members.</li></ol>                                                           

<p>The different sections appearing in the <b>Project Issues</b> page indicate the following issue tracking options available to you:
<blockquote>
<dl>
<dt><a href="ddIssues_Query.html"><b>Query Database of Issues</b></a> <dd>Search project issues by number, keywords, assignee, or other criteria.
<dt><a href="ddIssues_EnterModify.html"><b>Enter An Issue</b></a> <dd>Write and commit an issue report to the database.
<dt><a href="ddIssues_Query.html#trackissue"><b>My Issues</b></a> <dd>View a list of project issues assigned to you.
<dt><a href="#useraccounts"><b>My Preferences</b></a> <dd>Configure your issue tracker user settings.</dd>     
</dl>
</blockquote>

<hr noshade size=1>
<a name="aboutIZ"></a><span class="InputHeader">About IssueZilla</span>
<p>
IssueZilla is the issue tracking tool used on this 
    site.&nbsp; While it is a variant of BugZilla -- a bug tracking system you 
    may already be familiar with-- IssueZilla is a more generalized tool for 
    tracking many different kinds of activities in collaborative development 
    projects. Additionally, IssueZilla does not require a separate login as BugZilla does.&nbsp; IssueZilla classifies issues into several types:
      <ul><a href="ddIssues_EnterModify.html#issue_type">
       <li>Defects (a.k.a. "bugs")
       <li>Enhancements
       <li>Features
       <li>Tasks
       <li>Patches</a> </li>
      </ul>
<p>
Each hosted project on this site has it's own, unique 
    issues database. For open source projects in IssueZilla, all registered 
    users may query, view, and report issues, while proprietary projects limit 
    access to project members. 
    <p>
Project members have additional permissions within IssueZilla to modify and reassign issues, as well as generate reports. Project members are also notified automatically by email whenever issues are assigned to them or&nbsp;there is activity on issues affecting&nbsp;their work.
<p>
  Entering the tasks you're planning to work on as issues helps you devise and follow a work plan. Because everyone is aware&nbsp;of each project member's area of work, you can avoid duplicating efforts and even help out or offer feedback to other project members. Effective issue tracking requires an understanding of the IssueZilla tool and a working knowledge of what constitutes a well-written issue report.
<p>

<hr noshade size=1>     
     <a name="useraccounts"><span class="InputHeader">Setting your issue tracking user preferences</span></a><p>

     <p>When you join a hosted development project on this site, you automatically get an IssueZilla account for access to that project's issues.

     <p>Information about your account is available either 
    by clicking the <strong>My Preferences</strong> link on the <b>Project Issues</b> page.&nbsp; Once you have entered 
    the issue tracking area of the site you can&nbsp;click on the <strong>Edit 
    prefs </strong> link in the Issue Tracking toolbar, which appears in all issue tracking screens. You have several options to change your user settings:
     <p>
     <dl>
      <dt><b>Email settings</b> 
       <dd>Controls your automatic email notification settings. 
      <dt><b>Page footer</b> 
       <dd>Include/exclude "My issues" or your named, custom queries in every IssueZilla page footer.
	  <dt><b>Permissions</b>
		<dd>Displays your issue tracking permissions but 
      cannot be changed because permissions are assigned by the Project Owner. 
      (See next section.)</dd>                     
	 </dl>
     
     <p>
<hr noshade size=1>
     <a name="permissions"><span class="InputHeader"> About issue tracking permissions</span></a>
<p>
Once a user&nbsp;becomes a member of a project, 
    he&nbsp;or she&nbsp;is granted additional IssueZilla 
    permissions beyond the default database query capabilities. Permissions can 
    be viewed by&nbsp;clicking on the&nbsp; <strong>My Preferences</strong> link on the <b>Project Issues</b> page, or the <strong>Edit Prefs 
    </strong> link in the Issue Tracking toolbar.
<p>
    Issue tracking permissions depend upon project role:&nbsp;
<ul>
<li>Observers can&nbsp;create and modify issues, 
      but&nbsp;can make changes to&nbsp;only their own issues. Observers have the ability to comment on any issue.&nbsp;
<p></p>
<li>Developers&nbsp;(code or content) can report and 
      modify&nbsp;their own and other project&nbsp; issues. If they have been 
      granted&nbsp;the "Can edit all aspects of any issue" permission, they have the ability to alter all issue characteristics, including milestones and issue assignments. 
<p></p>
<li>Project initiators automatically are granted&nbsp;administrative level IssueZilla&nbsp; permissions&nbsp;with additional&nbsp;rights to 
      configure issue tracking for the&nbsp;project.&nbsp;Project initiators can also assign 
      IssueZilla-specific permissions to other project members.</li>                               
</ul>
                  Additional permissions can be requested through the project owner.&nbsp;You may need to request a new project role.
     <p>
       Permissions affect the&nbsp;lifecycle and resolution of issues. For example, if you have the "Can confirm an issue" permission, then you can change the status of any <b>UNCONFIRMED</b> issue to <b>NEW</b>             . A change in issue status sends an alert to the owner and all other project members associated with the issue.To understand more about issue status, read more about the 
     <a href="issue_lifecycle.html">lifecycle of issues</a>.
     <p>
    
<hr noshade size=1>
<a name="Moreinfo"></a><span class="InputHeader">More resources about issues and issue tracking</span>
d42 7
a48 9
      <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" target="_new">BugZilla FAQ</a>**
      <li><a href="http://www.mozilla.org/quality/help/bugzilla-helper.html" target="_new">Step-by-step help for bug entry</a>**
      <li><a href="http://www.mozilla.org/quality/bug-writing-guidelines.html" target="_new">BugZilla guide to writing good bug reports</a>**
	  <li><a href="http://scarab.tigris.org" target="_new">Scarab</a>, an open source issue tracking development 
      project</li>       
d50 64
d115 1
a115 1
     <p><font size="-1"><b><i>**</i></b>   These links listed are associated with BugZilla, but offer useful bug-writing guidelines that are applicable to IssueZilla. 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>
d117 1
a117 1
<p>If you are interested in finding out about other bug tracking systems being developed, see the <a href="http://scarab.tigris.org" target="_new">scarab</a> open source project.
d119 2
a120 2
     <p><font size="-1"><b><i>A note about IssueZilla and 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 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>
<p>
d122 81
a202 11
<hr noshade size=1>
<a href="/servlets/HelpTOC">Back to main Help index</a>
</span>
    <p></p>
    <p></p>
    <p></p>
    <p></p>
    <p></p>
    <p></p></p>
</tr>
</table>
d205 2
@


1.7
log
@updating version to reflect latest content changes
@
text
@d23 1
a23 1
		<dd><a href="ProjectMembers.html">Project Members</a>
d25 1
a25 1
		<dd><a href="ProjectDocuments.html">Project Documentation</a>
@


1.7.6.1
log
@updating branch with latest help files
@
text
@d23 1
a23 1
	<dd><a href="ProjectMemberList.html">Project Members</a>
d25 1
a25 1
	<dd><a href="ProjectDocuments.html">Project Documentation</a>
@


1.6
log
@Edited by Thena
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 185
a185 184
<HTML>
<HEAD>

<TITLE>Project Resources for Project Members</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" WIDTH="100%" >
  <TR>
   
<P>
<SPAN CLASS=HEADER>Project Issues</SPAN>
<P>
<SPAN CLASS="PlainText"><STRONG>Project resources for project members: Index 
    </STRONG> 
         
    
<P>
<UL>
	<DL>
       	<DT><A href="ProjectMemberResources.html">Project resources for members</A></A>
        <DD><A href="ProjectHome.html">Project Home Page</A>
        <DD><A href="ProjectNews.html">Project News</A>
        <DD><A href="ProjectDownload.html">Project Download</A>
		<DD><A href="ProjectMembers.html">Project Members</A>
        <DD><A href="ProjectMail.html">Project Mailing Lists</A>
        <DD><A href="ProjectSource.html">Project Source Code</A>
        <DD><B>You are here: Project Issues</B>
			<UL>
				<LI><A href="#accessissues">Accessing project issues
				<LI><A href="#aboutIZ">About the IssueZilla tool</A>
    			<LI><A href="#useraccounts">Setting your issue tracking user preferences</A>
     			<LI><A href="#permissions">About your issue tracking permissions</A></LI>
			</UL>
	<DT><A href="/servlets/HelpTOC">Back to main Help index</A></DT>
	</DL>
</UL>

<P>
<B>More help on issue tracking</B>
<UL>
	<DL>
     <DT><A href="ddIssues_EnterModify.html">Entering and modifying issues</A>
     <DT><A href="ddIssues_Query.html">Querying and tracking issues</A>
     <DT><A href="ddIssues_Reports.html">Generating status reports about project issues</A>
     <DT><A href="#Moreinfo">More how-to information about issues and issue tracking</A></DT> 
	 </DL>
</UL>

<P>
<HR NOSHADE SIZE=1>
<A NAME="accessissues"></A><SPAN CLASS="InputHeader">Accessing project issues</SPAN>
<P>
All development activities for each project hosted on 
    this site are tracked in a unique database. 
The <STRONG>Issue Tracking </STRONG>  link in the Project Resources toolbar displays the <B>Project Issues</B>           
          page, the entry point to that project's 
    issue database. Issue tracking provides the following benefits:&nbsp;
    <OL><P><li> Ability to chart&nbsp;the progress of individuals and the overall project
    
    
      <LI>Tracking and maintainance&nbsp;of project history
      <LI>Generation and repoting of&nbsp;ongoing to-do lists for all project 
    members.</LI></OL>                                                           

<P>The different sections appearing in the <B>Project Issues</B> page indicate the following issue tracking options available to you:
<DL>
<DT><A href="ddIssues_Query.html"><B>Query Database of Issues</B></A> <DD>Search project issues by number, keywords, assignee, or other criteria.
<DT><A href="ddIssues_EnterModify.html"><B>Enter An Issue</B></A> <DD>Write and commit an issue report to the database.
<DT><A href="ddIssues_Query.html#trackissue"><B>My Issues</B></A> <DD>View a list of project issues assigned to you.
<DT><A href="#useraccounts"><B>My Preferences</B></A> <DD>Configure your issue tracker user settings.</DD>     
</DL>

<HR NOSHADE SIZE=1>
<A NAME="aboutIZ"></A><SPAN CLASS="InputHeader">About IssueZilla</SPAN>
<P>
IssueZilla is the issue tracking tool used on this 
    site.&nbsp; While it is a variant of BugZilla -- a bug tracking system you 
    may already be familiar with-- IssueZilla is a more generalized tool for 
    tracking many different kinds of activities in collaborative development 
    projects. Additionally, IssueZilla does not require a seperate login as BugZilla does.&nbsp; IssueZilla classifies issues into several types:
      <UL><A href="ddIssues_EnterModify.html#issue_type">
       <LI>Defects (a.k.a. "bugs")
       <LI>Enhancements
       <LI>Features
       <LI>Tasks
       <LI>Patches</A> </LI>
      </UL>
<P>
Each hosted project on this site has it's own, unique 
    issues database. For open source projects in IssueZilla, all registered 
    users may query, view, and report issues, while proprietary projects limit 
    access to project members. 
    <P>
Project members have additional permissions within IssueZilla to modify and reassign issues, as well as generate reports. Project members are also notified automatically by email whenever issues are assigned to them or&nbsp;there is activity on issues affecting&nbsp;their work.
<P>
  Entering the tasks you're planning to work on as issues helps you devise and follow a work plan. Because everyone is aware&nbsp;of each project member's area of work, you can avoid duplicating efforts and even help out or offer feedback to other project members. Effective issue tracking requires an understanding of the IssueZilla tool and a working knowledge of what constitutes a well-written issue report.
<P>

<HR NOSHADE SIZE=1>     
     <A NAME="useraccounts"><SPAN CLASS="InputHeader">Setting your issue tracking user preferences</SPAN></A><P>

     <P>When you join a hosted development project on this site, you automatically get an IssueZilla account for access to that project's issues.

     <P>Information about your account is available either 
    by clicking the <STRONG>My Preferences</STRONG> link on the <B>Project Issues</B> page.&nbsp; Once you have entered 
    the issue tracking area of the site you can&nbsp;click on the <STRONG>Edit 
    prefs </STRONG> link in the Issue Tracking toolbar, which appears in all issue tracking screens. You have several options to change your user settings:
     <P>
     <DL>
      <DT><B>Email settings</B> 
       <DD>Controls your automatic email notification settings. 
      <DT><B>Page footer</B> 
       <DD>Include/exclude "My issues" or your named, custom queries in every IssueZilla page footer.
	  <DT><B>Permissions</B>
		<DD>Displays your issue tracking permissions but 
      cannot be changed because permissions are assigned by the Project Owner. 
      (See next section.)</DD>                     
	 </DL>
     
     <P>
<HR NOSHADE SIZE=1>
     <A NAME="permissions"><SPAN CLASS="InputHeader"> About issue tracking permissions</SPAN></A>
<P>
Once a user&nbsp;becomes a member of a project, 
    he&nbsp;or she&nbsp;is granted additional IssueZilla 
    permissions beyond the default database query capabilities. Permissions can 
    be viewed by&nbsp;clicking on the&nbsp; <STRONG>My Preferences</STRONG> link on the <B>Project Issues</B> page, or the <STRONG>Edit Prefs 
    </STRONG> link in the Issue Tracking toolbar.
<P>
    Issue tracking permissions depend upon project role:&nbsp;
<UL>
<LI>Observers can&nbsp;create and modify issues, 
      but&nbsp;can make changes to&nbsp;only their own issues. Observers have the ability to comment on any issue.&nbsp;
<P></P>
<LI>Developers&nbsp;(code or content) can report and 
      modify&nbsp;their own and other project&nbsp; issues. If they have been 
      granted&nbsp;the "Can edit all aspects of any issue" permission, they have the ability to alter all issue characteristics, including milestones and issue assignments. 
<P></P>
<LI>Project initiators automatically are granted&nbsp;administrative level IssueZilla&nbsp; permissions&nbsp;with additional&nbsp;rights to 
      configure issue tracking for the&nbsp;project.&nbsp;Project initiators can also assign 
      IssueZilla-specific permissions to other project members.</LI>                               
</UL>
                  Additional permissions can be requested through the project owner.&nbsp;You may need to request a new project role.
     <P>
       Permissions affect the&nbsp;lifecycle and resolution of issues. For example, if you have the "Can confirm an issue" permission, then you can change the status of any <B>UNCONFIRMED</B> issue to <B>NEW</B>             . A change in issue status sends an alert to the owner and all other project members associated with the issue.To understand more about issue status, read more about the 
     <A href="issue_lifecycle.html">lifecycle of issues</A>.
     <P>
    
<HR NOSHADE SIZE=1>
<A NAME="Moreinfo"></A><SPAN CLASS="InputHeader">More resources about issues and issue tracking</SPAN>

     <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" TARGET="_new">BugZilla FAQ</A>**
      <LI><A HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html" TARGET="_new">Step-by-step help for bug entry</A>**
      <LI><A HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html" TARGET="_new">BugZilla guide to writing good bug reports</A>**
	  <LI><A HREF="http://scarab.tigris.org" TARGET="_new">Scarab</A>, an open source issue tracking development 
      project</LI>       
     </UL>

     <P><FONT SIZE="-1"><B><I>**</I></B>   These links listed are associated with BugZilla, but offer useful bug-writing guidelines that are applicable to IssueZilla. 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>If you are interested in finding out about other bug tracking systems being developed, see the <A HREF="http://scarab.tigris.org" TARGET="_new">scarab</A> open source project.

     <P><FONT SIZE="-1"><B><I>A note about IssueZilla and 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 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>
<P>

<HR NOSHADE SIZE=1>
<A href="/servlets/HelpTOC">Back to main Help index</A>
</SPAN>
    <P></P>
    <P></P>
    <P></P>
    <P></P>
    <P></P>
    <P></P></P>
</TR>
</TABLE>
</BODY>
</HTML>
@


1.5
log
@revised doc index format
@
text
@d1 184
a184 143
<HTML>
<HEAD>

<TITLE>Project Resources for Project Members</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
   
<P>
<SPAN CLASS=HEADER>Project Issues</SPAN>
<P>
<SPAN CLASS="PlainText"><B>Project resources for project members: Index</B>
<P>
<UL>
	<DL>
       	<DT><A HREF="ProjectMemberResources.html">Project resources for members</A></A></DT>
        <DD><A HREF="ProjectHome.html">Project Home Page</A></DD>
        <DD><A HREF="ProjectNews.html">Project News</A></DD>
        <DD><A HREF="ProjectDownload.html">Project Download</A></DD>
		<DD><A HREF="ProjectMembers.html">Project Members</A></DD>
        <DD><A HREF="ProjectMail.html">Project Mailing Lists</A>
        <DD><A HREF="ProjectSource.html">Project Source Code</A></DD>
        <DD><B>You are here: Project Issues</B></DD>
			<UL>
				<LI><A HREF="#accessissues">Accessing project issues
				<LI><A HREF="#aboutIZ">About the IssueZilla tool</A>
    			<LI><A HREF="#useraccounts">Setting your issue tracking user preferences</A>
     			<LI><A HREF="#permissions">About your issue tracking permissions</A>
			</UL>
	<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
	</DL>
</UL>

<P>
<B>More help on issue tracking</B>
<UL>
	<DL>
     <DT><A HREF="ddIssues_EnterModify.html">Entering and modifying issues</A>
     <DT><A HREF="ddIssues_Query.html">Querying and tracking issues</A>
     <DT><A HREF="ddIssues_Reports.html">Generating status reports about project issues</A>
     <DT><A HREF="#Moreinfo">More how-to information about issues and issue tracking</A> 
	 </DL>
</UL>

<P>
<HR NOSHADE SIZE=1>
<A NAME="accessissues"></A><SPAN CLASS="InputHeader">Accessing project issues</SPAN>
<P>
The <I>Issue Tracking</I> link in the Project Resources toolbar displays the the <B>Project Issues</B> page, the entry point to that project's issue database. All development activities for each project hosted on this site are tracked in a unique database. The benefits of issue tracking are that it charts the progress both of individuals and the overall project, maintains a project history, and in practice generates the ongoing to-do lists for all project members.

<P>The different sections appearing in the <B>Project Issues</B> page indicate issue tracking options available to you:
<DL>
<DT><A HREF="ddIssues_Query.html"><B>Query Database of Issues</B></A> <DD>Search project issues by number, keywords, assignee, or other criteria.
<DT><A HREF="ddIssues_EnterModify.html"><B>Enter An Issue</B></A> <DD>Write and commit an issue report to the database.
<DT><A HREF="ddIssues_Query.html#trackissue"><B>My Issues</B></A> <DD>View a list of project issues assigned to you.
<DT><A HREF="#useraccounts"><B>My Preferences</B></A> <DD>Configure your issue tracker user settings.
</DL>

<HR NOSHADE SIZE=1>
<A NAME="aboutIZ"></A><SPAN CLASS="InputHeader">About IssueZilla</SPAN>
<P>
The tool used on this site for issue tracking is IssueZilla, a variant of BugZilla -- a bug tracking system you may already be familiar with. There are several important differences, the most important one being that IssueZilla is a more generalized tool for tracking many different kinds of activities -- not only code-based <I>bugs</I> -- in collaborative development projects. IssueZilla classifies issues into several types:
      <UL><A HREF="ddIssues_EnterModify.html#issue_type">
       <LI>defects (a.k.a. "bugs")
       <LI>enhancements
       <LI>features
       <LI>tasks
       <LI>patches</A>
      </UL>
<P>
Another important difference between IssueZilla and BugZilla is that you do not have to log in separately to IssueZilla. Each hosted project on this site has its own unique issues database. For open source projects here, all registered users may query, view, and report issues. Issue databases for proprietary projects, however, are limited to project members.
<P>
As a project member, you have additional permissions within IssueZilla to modify and reassign issues, as well as generate reports. You are also notified automatically by email whenever issues are assigned to you and whenever there is activity on issues affecting your work.
<P>
Entering the tasks you're planning to work on as issues helps you devise and follow a 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 other project members. Effective issue tracking requires an understanding of the IssueZilla tool and a working knowledge of what constitutes a well-written issue report.
<P>

<HR NOSHADE SIZE=1>     
     <A NAME="useraccounts"><SPAN CLASS="InputHeader">Setting your issue tracking user preferences</SPAN></A><P>

     <P>When you join a hosted development project on this site, you automatically get an IssueZilla account for access to that project's issues.

     <P>Information about your account is available either by clicking the <I>My Preferences</I> link on the <B>Project Issues</B> page, or the <I>Edit prefs</I> link in the Issue Tracking toolbar, which appears in all issue tracking screens. You have several options to change your user settings:
     <P>
     <DL>
      <DT><B>Email settings</B> 
       <DD>Controls your automatic email notification settings. 
      <DT><B>Page footer</B> 
       <DD>Include/exclude "My issues" or your named, custom queries in every IssueZilla page footer.
	  <DT><B>Permissions</B>
		<DD>Displays your issue tracking permissions but cannot be changed  because permissions are assigned by the Project Owner. (See next section.) 
	 </DL>
     
     <P>
<HR NOSHADE SIZE=1>
     <A NAME="permissions"><SPAN CLASS="InputHeader">About your issue tracking permissions</SPAN></A>
<P>
Once you become a member of a project, you gain additional IssueZilla permissions beyond querying the issue database. You can view these using the <I>My Preferences</I> link on the <B>Project Issues</B> page, or the <I>Edit prefs</I> link in the Issue Tracking toolbar.
<P>
Your issue tracking permissions depend upon your role in a project:
<UL>
<LI>If you are an observer, you can report new issues and modify issues, <I>but you can only make changes to your own issues</I>. You can, however, comment on any issue.
<P>
<LI>If you are a developer (code or content), you can report and modify your own <I>and other project members'</I> issues. If you have the "Can edit all aspects of any issue" permission, then you can tweak anything about any issue, including milestones and issue assignments. 
<P>
<LI>If you start your own project, you become an administrative level IssueZilla user with additional permissions to configure your project's issue tracking. You can also assign IssueZilla-specific permissions to other project members.
</UL>
Whatever your role in a project, if you really feel that you ought to have additional IssueZilla permissions, the project owner is the person to contact. You may need to request a new project role.
     <P>
Permissions are important because they are linked to the lifecycle and resolution of issues. For example, if you have the "Can confirm an issue" permission, then you can change the status of any <B>UNCONFIRMED</B> issue to <B>NEW</B>. This is critical because it serves as a green light to the person the issue is assigned to (and anyone else connected with the issue) by confirming that the issue is "real." To understand more about issue status, read more about the 
     <A HREF="issue_lifecycle.html">lifecycle of issues</A>.
     <P>
    
<HR NOSHADE SIZE=1>
<A NAME="Moreinfo"></A><SPAN CLASS="InputHeader">More resources about issues and issue tracking</SPAN>

     <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" TARGET="_new">BugZilla FAQ</A>**
      <LI><A HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html" TARGET="_new">Step-by-step help for bug entry</A>**
      <LI><A HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html" TARGET="_new">BugZilla guide to writing good bug reports</A>**
	  <LI><A HREF="http://scarab.tigris.org" TARGET="_new">Scarab</A>, an open source issue tracking development project
     </UL>

     <P><FONT SIZE="-1"><B><I>**</I></B> These documentation links listed above are associated with BugZilla, but offer useful bug-writing guidelines that are applicable to IssueZilla. 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>If you are interested in finding out about other bug tracking systems being developed, see the <A HREF="http://scarab.tigris.org" TARGET="_new">scarab</A> open source project.

     <P><FONT SIZE="-1"><B><I>A note about IssueZilla and 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>
<P>

<HR NOSHADE SIZE=1>
<A HREF="/servlets/HelpTOC">Back to main Help index</A>
</SPAN>
</TR>
</TABLE>
</BODY>
</HTML>
@


1.4
log
@added <title> tags to all files
@
text
@a10 2

<SPAN CLASS="PlainText">Project resources for project members</SPAN>
d13 3
a15 2
<SPAN CLASS="PlainText">

@


1.3
log
@removed window's nasty line breaks, and corrected more links in HelpBox files
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 7
d143 2
@


1.2
log
@updated for new help format
@
text
@d1 135
a135 135
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
   

<SPAN CLASS="PlainText">Project resources for project members</SPAN>
<P>
<SPAN CLASS=HEADER>Project Issues</SPAN>
<SPAN CLASS="PlainText">

<UL>
	<DL>
       	<DT><A HREF="ProjectMemberResources.html">Project resources for members</A></A></DT>
        <DD><A HREF="ProjectHome.html">Project Home Page</A></DD>
        <DD><A HREF="ProjectNews.html">Project News</A></DD>
        <DD><A HREF="ProjectDownload.html">Project Download</A></DD>
		<DD><A HREF="ProjectMembers.html">Project Members</A></DD>
        <DD><A HREF="ProjectMail.html">Project Mailing Lists</A>
        <DD><A HREF="ProjectSource.html">Project Source Code</A></DD>
        <DD><B>You are here: Project Issues</B></DD>
			<UL>
				<LI><A HREF="#accessissues">Accessing project issues
				<LI><A HREF="#aboutIZ">About the IssueZilla tool</A>
    			<LI><A HREF="#useraccounts">Setting your issue tracking user preferences</A>
     			<LI><A HREF="#permissions">About your issue tracking permissions</A>
			</UL>
	<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
	</DL>
</UL>

<P>
<B>More help on issue tracking</B>
<UL>
	<DL>
     <DT><A HREF="ddIssues_EnterModify.html">Entering and modifying issues</A>
     <DT><A HREF="ddIssues_Query.html">Querying and tracking issues</A>
     <DT><A HREF="ddIssues_Reports.html">Generating status reports about project issues</A>
     <DT><A HREF="#Moreinfo">More how-to information about issues and issue tracking</A> 
	 </DL>
</UL>

<P>
<HR NOSHADE SIZE=1>
<A NAME="accessissues"></A><SPAN CLASS="InputHeader">Accessing project issues</SPAN>
<P>
The <I>Issue Tracking</I> link in the Project Resources toolbar displays the the <B>Project Issues</B> page, the entry point to that project's issue database. All development activities for each project hosted on this site are tracked in a unique database. The benefits of issue tracking are that it charts the progress both of individuals and the overall project, maintains a project history, and in practice generates the ongoing to-do lists for all project members.

<P>The different sections appearing in the <B>Project Issues</B> page indicate issue tracking options available to you:
<DL>
<DT><A HREF="ddIssues_Query.html"><B>Query Database of Issues</B></A> <DD>Search project issues by number, keywords, assignee, or other criteria.
<DT><A HREF="ddIssues_EnterModify.html"><B>Enter An Issue</B></A> <DD>Write and commit an issue report to the database.
<DT><A HREF="ddIssues_Query.html#trackissue"><B>My Issues</B></A> <DD>View a list of project issues assigned to you.
<DT><A HREF="#useraccounts"><B>My Preferences</B></A> <DD>Configure your issue tracker user settings.
</DL>

<HR NOSHADE SIZE=1>
<A NAME="aboutIZ"></A><SPAN CLASS="InputHeader">About IssueZilla</SPAN>
<P>
The tool used on this site for issue tracking is IssueZilla, a variant of BugZilla -- a bug tracking system you may already be familiar with. There are several important differences, the most important one being that IssueZilla is a more generalized tool for tracking many different kinds of activities -- not only code-based <I>bugs</I> -- in collaborative development projects. IssueZilla classifies issues into several types:
      <UL><A HREF="ddIssues_EnterModify.html#issue_type">
       <LI>defects (a.k.a. "bugs")
       <LI>enhancements
       <LI>features
       <LI>tasks
       <LI>patches</A>
      </UL>
<P>
Another important difference between IssueZilla and BugZilla is that you do not have to log in separately to IssueZilla. Each hosted project on this site has its own unique issues database. For open source projects here, all registered users may query, view, and report issues. Issue databases for proprietary projects, however, are limited to project members.
<P>
As a project member, you have additional permissions within IssueZilla to modify and reassign issues, as well as generate reports. You are also notified automatically by email whenever issues are assigned to you and whenever there is activity on issues affecting your work.
<P>
Entering the tasks you're planning to work on as issues helps you devise and follow a 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 other project members. Effective issue tracking requires an understanding of the IssueZilla tool and a working knowledge of what constitutes a well-written issue report.
<P>

<HR NOSHADE SIZE=1>     
     <A NAME="useraccounts"><SPAN CLASS="InputHeader">Setting your issue tracking user preferences</SPAN></A><P>

     <P>When you join a hosted development project on this site, you automatically get an IssueZilla account for access to that project's issues.

     <P>Information about your account is available either by clicking the <I>My Preferences</I> link on the <B>Project Issues</B> page, or the <I>Edit prefs</I> link in the Issue Tracking toolbar, which appears in all issue tracking screens. You have several options to change your user settings:
     <P>
     <DL>
      <DT><B>Email settings</B> 
       <DD>Controls your automatic email notification settings. 
      <DT><B>Page footer</B> 
       <DD>Include/exclude "My issues" or your named, custom queries in every IssueZilla page footer.
	  <DT><B>Permissions</B>
		<DD>Displays your issue tracking permissions but cannot be changed  because permissions are assigned by the Project Owner. (See next section.) 
	 </DL>
     
     <P>
<HR NOSHADE SIZE=1>
     <A NAME="permissions"><SPAN CLASS="InputHeader">About your issue tracking permissions</SPAN></A>
<P>
Once you become a member of a project, you gain additional IssueZilla permissions beyond querying the issue database. You can view these using the <I>My Preferences</I> link on the <B>Project Issues</B> page, or the <I>Edit prefs</I> link in the Issue Tracking toolbar.
<P>
Your issue tracking permissions depend upon your role in a project:
<UL>
<LI>If you are an observer, you can report new issues and modify issues, <I>but you can only make changes to your own issues</I>. You can, however, comment on any issue.
<P>
<LI>If you are a developer (code or content), you can report and modify your own <I>and other project members'</I> issues. If you have the "Can edit all aspects of any issue" permission, then you can tweak anything about any issue, including milestones and issue assignments. 
<P>
<LI>If you start your own project, you become an administrative level IssueZilla user with additional permissions to configure your project's issue tracking. You can also assign IssueZilla-specific permissions to other project members.
</UL>
Whatever your role in a project, if you really feel that you ought to have additional IssueZilla permissions, the project owner is the person to contact. You may need to request a new project role.
     <P>
Permissions are important because they are linked to the lifecycle and resolution of issues. For example, if you have the "Can confirm an issue" permission, then you can change the status of any <B>UNCONFIRMED</B> issue to <B>NEW</B>. This is critical because it serves as a green light to the person the issue is assigned to (and anyone else connected with the issue) by confirming that the issue is "real." To understand more about issue status, read more about the 
     <A HREF="issue_lifecycle.html">lifecycle of issues</A>.
     <P>
    
<HR NOSHADE SIZE=1>
<A NAME="Moreinfo"></A><SPAN CLASS="InputHeader">More resources about issues and issue tracking</SPAN>

     <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" TARGET="_new">BugZilla FAQ</A>**
      <LI><A HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html" TARGET="_new">Step-by-step help for bug entry</A>**
      <LI><A HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html" TARGET="_new">BugZilla guide to writing good bug reports</A>**
	  <LI><A HREF="http://scarab.tigris.org" TARGET="_new">Scarab</A>, an open source issue tracking development project
     </UL>

     <P><FONT SIZE="-1"><B><I>**</I></B> These documentation links listed above are associated with BugZilla, but offer useful bug-writing guidelines that are applicable to IssueZilla. 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>If you are interested in finding out about other bug tracking systems being developed, see the <A HREF="http://scarab.tigris.org" TARGET="_new">scarab</A> open source project.

     <P><FONT SIZE="-1"><B><I>A note about IssueZilla and 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>
<P>

<HR NOSHADE SIZE=1>
<A HREF="/servlets/HelpTOC">Back to main Help index</A>
</SPAN>
</TR>
</TABLE>
@


1.1
log
@new and revised help documentation for v1.0
@
text
@d5 1
a5 1
<span class="PlainText">Project resources for project members</SPAN>
d7 2
a8 2
<SPAN class=Header>Project Issues</SPAN>
<span class="PlainText">
a9 2
<P>
<B>Contents of this document</B>
d12 15
a26 4
  	<DT><A HREF="#accessissues">Accessing project issues
	<DT><A HREF="#aboutIZ">About the IssueZilla tool</A>
    <DT><A HREF="#useraccounts">Setting your issue tracking user preferences</A>
     <DT><A HREF="#permissions">About your issue tracking permissions</A>
d29 1
d40 1
d42 2
a43 2
<HR noShade SIZE=1>
<A NAME="accessissues"></A><span class="InputHeader">Accessing project issues</SPAN>
d55 2
a56 2
<HR noShade SIZE=1>
<A NAME="aboutIZ"></A><span class="InputHeader">About IssueZilla</SPAN>
d74 2
a75 2
<HR noShade SIZE=1>     
     <A NAME="useraccounts"><span class="InputHeader">Setting your issue tracking user preferences</span></A><P>
d77 1
a77 1
     <p>When you join a hosted development project on this site, you automatically get an IssueZilla account for access to that project's issues.
d79 2
a80 2
     <p>Information about your account is available either by clicking the <I>My Preferences</I> link on the <B>Project Issues</B> page, or the <I>Edit prefs</I> link in the Issue Tracking toolbar, which appears in all issue tracking screens. You have several options to change your user settings:
     <p>
d90 3
a92 3
     <p>
<HR noShade SIZE=1>
     <A NAME="permissions"><span class="InputHeader">About your issue tracking permissions</span></A>
d105 1
a105 1
     <p>
d108 1
a108 1
     <p>
d110 2
a111 2
<HR noShade SIZE=1>
<A NAME="Moreinfo"></A><span class="InputHeader">More resources about issues and issue tracking</span>
d118 4
a121 4
      <LI><A HREF="http://www.trilobyte.net/barnsons/FAQ.html" target="_new">BugZilla FAQ</A>**
      <LI><A HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html" target="_new">Step-by-step help for bug entry</A>**
      <LI><A HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html" target="_new">BugZilla guide to writing good bug reports</A>**
	  <LI><A HREF="http://scarab.tigris.org" target="_new">Scarab</A>, an open source issue tracking development project
d124 1
a124 1
     <P><FONT SIZE="-1"><B><I>**</I></B> These documentation links listed above are associated with BugZilla, but offer useful bug-writing guidelines that are applicable to IssueZilla. 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>
d126 1
a126 1
<P>If you are interested in finding out about other bug tracking systems being developed, see the <a href="http://scarab.tigris.org" target="_new">scarab</A> open source project.
d131 2
a132 2
<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>
@

