head	1.10;
access;
symbols
	TIGRIS_1_1_0RC2:1.7
	TIGRIS_1_1_0RC1:1.7
	TIGRIS_1_1:1.7.0.4
	TIGRIS_1_0_8:1.7
	TIGRIS_1_0_8RC3:1.7
	TIGRIS_1_0_8RC2:1.7
	TIGRIS_1_0_8RC1:1.7
	TIGRIS_1_0_7:1.7
	TIGRIS_1_0_7RC3:1.7
	TIGRIS_1_0_7RC2:1.7
	TIGRIS_1_0_7RC1:1.7
	TIGRIS_1_0_6:1.7
	TIGRIS_1_0_6RC5:1.7
	TIGRIS_1_0_6RC4:1.7
	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.10
date	2001.07.31.23.48.57;	author csjank;	state Exp;
branches;
next	1.9;

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

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

1.7
date	2001.03.12.08.31.55;	author lori;	state Exp;
branches;
next	1.6;

1.6
date	2001.02.22.01.00.55;	author lori;	state Exp;
branches;
next	1.5;

1.5
date	2001.02.15.21.43.43;	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.40.17;	author lori;	state Exp;
branches;
next	1.1;

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


desc
@@


1.10
log
@minor edit to resolve iz 3040
@
text
@  <div class="docs" id="projectownerissues">
   <h2>Tracking project issues</h2>

   <div class="toc">
    <h3>Project help for project owner administration: Index</h3>

    <ul>
     <li>
      <a href="ProjectOwnerAdmin.html">Project owner administration</a> 

      <ul>
       <li><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></li>

       <li><a href="ProjectOwnerNews.html">Managing project site news</a></li>

       <li><a href="ProjectOwnerFiles.html">Managing project files</a></li>

       <li><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a></li>

       <li><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a></li>

       <li><a href="ProjectOwnerDocuments.html">Managing project documentation</a></li>

       <li><a href="ProjectOwnerSource.html">Managing project source code</a></li>

       <li>
        <strong>You are here:</strong> Tracking project issues 

        <ul>
         <li><a href="#adminpermissions">About administrative issue tracking permissions</a></li>

         <li><a href="#adminconfigure">Configuring IssueZilla's administrative options</a></li>

         <li><a href="#admintips">Tips and tricks for issue management</a></li>
        </ul>
       </li>
      </ul>
     </li>
    </ul>

    <h3>Issue tracker tool documentation</h3>

    <ul>
     <li><a href="ProjectIssues.html">Project Issues page help</a></li>

     <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>
    </ul>
   </div>

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

   <h3><a id="adminpermissions" name="adminpermissions">Issue tracking administration</a></h3>

   <p>Because you are a Project Owner, you automatically have administrative permissions in IssueZilla to manage and track your project's issues. You can access these administrative options two different ways:</p>

   <ul>
    <li>Your view of the <b>Project Issues</b> page includes additional sections to <i>Edit Users</i>, <i>Edit Groups</i>, and <i>Edit Components</i>.</li>

    <li>All administrative options are included in the Issue Tracking toolbar, which appears in your view of all issue tracking screens.</li>
   </ul>

   <p>Your role of Project Owner gives you the ability to configure almost every element of IssueZilla. Descriptions of these options and their default settings follows. Probably the most significant permission you have is the ability to edit the issue tracking permissions of all other users on your project. This can include delegating some of these administrative permissions to other users to help manage and plan the project workload.</p>

   <p>If one of your project members builds a solid track record of committing issues that get confirmed, this is probably a person who understands the project and the issue tracking system well enough to be granted the "Can confirm an issue" permission. As a project owner, you can and should use IssueZilla to track this kind of information about project participants to help you manage project issues effectively.</p>

   <p>To learn how to assign issue tracking permissions to project members, see "Users" in the next section</p>

   <h3><a id="adminconfigure" name="adminconfigure">Configuring IssueZilla's administrative options</a></h3>

   
  <dl> 
    <dt>Prefs (Preferences)</dt>
    <dd> 
      <p>Lets you configure some aspects of your issue tracking functionality 
        and display environment, including:</p>
      <ul>
        <li>Email settings for automatic issue email notifications to you.</li>
        <li>Page footer links to be included in your query results screens.</li>
        <li>Permissions assigned to you as the default issue tracking administrator. 
          (You control these permissions for all members of your project through 
          the <i>Users</i> option in the Issue Tracking toolbar.)</li>
      </ul>
    </dd>
    <dt>Sanity check</dt>
    <dd>An automated process that checks for and identifies any anomalies in your 
      project's issues database, such as conflicting dependencies, committed issue 
      errors, and correct references between issue reporters and user profiles. 
      You can run the sanity check to check for corruption or invalid enteries 
      in your issue database.</dd>
    <dt>Users</dt>
    <dd>A text string field lets you access the user edit screen either by filtering 
      for specific users or leaving it blank to access the full list of users 
      after clicking the "Submit" button. Clicking on listed user's link displays 
      another edit screen where you can check and uncheck permissions options.</dd>
    <dt>Components</dt>
    <dd>A component selection screen that lets you create, define, edit, add, 
      and delete project components and subcomponents. Clicking on a component 
      link in the list displays another edit screen where you can configure that 
      particular component or subcomponent.</dd>
    <dt>Groups</dt>
    <dd>A group selection screen that lets you create, define, and delete groups 
      specifically for issue tracking purposes, and assign project member users 
      to groups. You can make changes to one, several, or all fields and submit 
      them all at once. Your project also includes a default set of groups pertaining 
      to issue tracking permissions.</dd>
    <dt>Keywords</dt>
    <dd>A keyword selection screen that lets you create, define, edit, and delete 
      regular expression keywords to be used for issue tracking groups and queries.</dd>
  </dl>

   <h3><a id="admintips" name="admintips">Tips and tricks for issue management</a></h3>

   <p>IssueZilla is a powerful tool for managing and tracking your project's development activities down to the fine-grained details. As with most tools, users develop inevitably develop shortcuts and tricks to compensate for particular aspects of the tool, or to tailor it to their specific needs. IssueZilla is no exception.</p>

   <p>What follows is a sampling of several tricks that have proved particularly useful to project managers or users with administrative issue tracking permissions:</p>

   <ul>
    <li>Avoid configuring the same management-level queries repeatedly by creating permanently displayed links to information you use constantly. For example, you can create a page of links for each project member's issue list, and for regularly used milestone or issue status queries.</li>

    <li>Because issues may not be deleted, you can create components or subcomponents named "issue graveyard" or "unknown" to collect dead or no longer applicable issues. IssueZilla's non-delete feature is actually a protective design feature since the ability to track such dead issues can sometimes come in handy, or at least preserve aspects of project history.</li>

    <li>Create a "not determined" milestone for project issues not yet tied to any particular project milestone date or release. Development project objectives and priorities tend to shift dynamically. This lets you identify and hold in reserve those issues affected by your project's evolution.</li>

    <li>Add a pseudo user known as "placeholder" (or some other equally obvious generic identity) who can "own" issues that you are not yet ready or able to assign to specific project members.</li>
   </ul>

   <div class="courtesylinks">
    <p><a href="ProjectOwnerAdmin.html">Back to Project Owner Administration help</a><br />
    <a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.9
log
@html usage revision
@
text
@d76 2
a77 1
   <dl>
d79 10
a88 11

    <dd>
     <p>Lets you configure some aspects of your issue tracking functionality and display environment, including:</p>

     <ul>
      <li>Email settings for automatic issue email notifications to you.</li>

      <li>Page footer links to be included in your query results screens.</li>

      <li>Permissions assigned to you as the default issue tracking administrator. (You control these permissions for all members of your project through the <i>Users</i> option in the Issue Tracking toolbar.)</li>
     </ul>
a89 1

d91 5
a95 3

    <dd>An automated process that checks for an identifies any anomalies in your project's issues database, such as conflicting dependencies, committed issue errors, and correct references between issue reporters and user profiles.</dd>

d97 4
a100 3

    <dd>A text string field lets you access the user edit screen either by filtering for specific users or leaving it blank to access the full list of users after clicking the "Submit" button. Clicking on listed user's link displays another edit screen where you can check and uncheck permissions options.</dd>

d102 4
a105 3

    <dd>A component selection screen that lets you create, define, edit, add, and delete project components and subcomponents. Clicking on a component link in the list displays another edit screen where you can configure that particular component or subcomponent.</dd>

d107 5
a111 3

    <dd>A group selection screen that lets you create, define, and delete groups specifically for issue tracking purposes, and assign project member users to groups. You can make changes to one, several, or all fields and submit them all at once. Your project also includes a default set of groups pertaining to issue tracking permissions.</dd>

d113 3
a115 3

    <dd>A keyword selection screen that lets you create, define, edit, and delete regular expression keywords to be used for issue tracking groups and queries.</dd>
   </dl>
@


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

 <body>
  <div class="docs" id="docid">
<h2>Tracking project issues</h2> 
d4 2
a5 1
  <p><b>Project help for project owner administration: Index</b></p>
d7 3
a9 1
  
d11 2
a12 3
  <div>
   <dl>
    <dt><a href="ProjectOwnerAdmin.html">Project owner administration</a></dt>
d14 1
a14 1
    <dd><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></dd>
d16 1
a16 1
    <dd><a href="ProjectOwnerNews.html">Managing project site news</a></dd>
d18 1
a18 1
    <dd><a href="ProjectOwnerFiles.html">Managing project files</a></dd>
d20 1
a20 1
    <dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a></dd>
d22 1
a22 1
    <dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a> `</dd>
d24 1
a24 1
    <dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a></dd>
d26 2
a27 1
    <dd><a href="ProjectOwnerSource.html">Managing project source code</a></dd>
d29 2
a30 2
    <dd>
     <b>You are here: Tracking project issues</b>
d32 1
a32 2
     <ul>
      <li><b><a href="#adminpermissions">About administrative issue tracking permissions</a></b></li>
d34 6
a39 1
      <li><b><a href="#adminconfigure">Configuring IssueZilla's administrative options</a></b></li>
d41 1
a41 3
      <li><b><a href="#admintips">Tips and tricks for issue management</a></b></li>
     </ul>
    </dd>
d43 2
a44 3
    <dt><a href="/servlets/HelpTOC">Back to main Help index</a></dt>
   </dl>
  </div>
d46 1
a46 1
  <p class="c2">Issue tracker tool documentation</p>
d48 1
a48 3
  <div>
   <dl>
    <dt><a href="ProjectIssues.html">Project Issues page help</a></dt>
d50 3
a52 1
    <dt><a href="ddIssues_EnterModify.html">Entering and modifying issues</a></dt>
d54 3
a56 1
    <dt><a href="ddIssues_Query.html">Querying and tracking issues</a></dt>
d58 1
a58 3
    <dt><a href="ddIssues_Reports.html">Generating status reports about project issues</a></dt>
   </dl>
  </div>
d60 1
a60 3
  
  
  <h3><a id="adminpermissions" name="adminpermissions">Issue tracking administration</a></h3> 
d62 2
a63 1
  
d65 2
a66 1
  <p>Because you are a Project Owner, you automatically have administrative permissions in IssueZilla to manage and track your project's issues. You can access these administrative options two different ways:</p>
d68 1
a68 3
  <ul>
   <li>
    Your view of the <b>Project Issues</b> page includes additional sections to <i>Edit Users</i>, <i>Edit Groups</i>, and <i>Edit Components</i>. 
d70 1
a70 2
    
   </li>
d72 1
a72 2
   <li>All administrative options are included in the Issue Tracking toolbar, which appears in your view of all issue tracking screens.</li>
  </ul>
d74 1
a74 1
  <p>Your role of Project Owner gives you the ability to configure almost every element of IssueZilla. Descriptions of these options and their default settings follows. Probably the most significant permission you have is the ability to edit the issue tracking permissions of all other users on your project. This can include delegating some of these administrative permissions to other users to help manage and plan the project workload.</p>
d76 2
a77 1
  <p>If one of your project members builds a solid track record of committing issues that get confirmed, this is probably a person who understands the project and the issue tracking system well enough to be granted the "Can confirm an issue" permission. As a project owner, you can and should use IssueZilla to track this kind of information about project participants to help you manage project issues effectively.</p>
d79 2
a80 3
  <p>To learn how to assign issue tracking permissions to project members, see "Users" in the next section</p>
  
  <h3><a id="adminconfigure" name="adminconfigure">Configuring IssueZilla's administrative options</a></h3> 
d82 2
a83 2
  <dl>
   <dt><b>Prefs</b> (Preferences)</dt>
d85 1
a85 2
   <dd>
    Lets you configure some aspects of your issue tracking functionality and display environment, including: 
d87 3
a89 1
    
d91 1
a91 2
    <ul>
     <li>Email settings for automatic issue email notifications to you.</li>
d93 1
a93 1
     <li>Page footer links to be included in your query results screens.</li>
d95 1
a95 3
     <li>Permissions assigned to you as the default issue tracking administrator. (You control these permissions for all members of your project through the <i>Users</i> option in the Issue Tracking toolbar.)</li>
    </ul>
   </dd>
d97 1
a97 1
   <dt class="c3">Sanity check</dt>
d99 1
a99 1
   <dd>An automated process that checks for an identifies any anomalies in your project's issues database, such as conflicting dependencies, committed issue errors, and correct references between issue reporters and user profiles.</dd>
d101 1
a101 1
   <dt class="c3">Users</dt>
d103 1
a103 1
   <dd>A text string field lets you access the user edit screen either by filtering for specific users or leaving it blank to access the full list of users after clicking the "Submit" button. Clicking on listed user's link displays another edit screen where you can check and uncheck permissions options.</dd>
d105 1
a105 1
   <dt class="c3">Components</dt>
d107 1
a107 1
   <dd>A component selection screen that lets you create, define, edit, add, and delete project components and subcomponents. Clicking on a component link in the list displays another edit screen where you can configure that particular component or subcomponent.</dd>
d109 2
a110 1
   <dt class="c3">Groups</dt>
d112 1
a112 1
   <dd>A group selection screen that lets you create, define, and delete groups specifically for issue tracking purposes, and assign project member users to groups. You can make changes to one, several, or all fields and submit them all at once. Your project also includes a default set of groups pertaining to issue tracking permissions.</dd>
d114 1
a114 1
   <dt class="c3">Keywords</dt>
d116 1
a116 4
   <dd>A keyword selection screen that lets you create, define, edit, and delete regular expression keywords to be used for issue tracking groups and queries.</dd>
  </dl>
  
  <h3><a id="admintips" name="admintips">Tips and tricks for issue management</a></h3> 
d118 2
a119 1
  <p>IssueZilla is a powerful tool for managing and tracking your project's development activities down to the fine-grained details. As with most tools, users develop inevitably develop shortcuts and tricks to compensate for particular aspects of the tool, or to tailor it to their specific needs. IssueZilla is no exception.</p>
d121 1
a121 1
  <p>What follows is a sampling of several tricks that have proved particularly useful to project managers or users with administrative issue tracking permissions:</p>
d123 1
a123 2
  <ul>
   <li>Avoid configuring the same management-level queries repeatedly by creating permanently displayed links to information you use constantly. For example, you can create a page of links for each project member's issue list, and for regularly used milestone or issue status queries.</li>
d125 2
a126 1
   <li>Because issues may not be deleted, you can create components or subcomponents named "issue graveyard" or "unknown" to collect dead or no longer applicable issues. IssueZilla's non-delete feature is actually a protective design feature since the ability to track such dead issues can sometimes come in handy, or at least preserve aspects of project history.</li>
d128 6
a133 12
   <li>Create a "not determined" milestone for project issues not yet tied to any particular project milestone date or release. Development project objectives and priorities tend to shift dynamically. This lets you identify and hold in reserve those issues affected by your project's evolution.</li>

   <li>Add a pseudo user known as "placeholder" (or some other equally obvious generic identity) who can "own" issues that you are not yet ready or able to assign to specific project members.</li>
  </ul>

  
  
 <div class="courtesylinks"> <a href="ProjectOwnerAdmin.html">Back to Project Owner Administration help</a><br />
<a href="/servlets/HelpTOC">Back to main Help index</a></div> 
 </div>
</body>
</html>
@


1.7
log
@fixed index; added link for ProjectOwnerDocuments.html
@
text
@d1 155
a155 2
<HTML>
<HEAD>
a156 1
<TITLE>Tracking Project Issues</TITLE>
a157 102
</HEAD>
<BODY>
<SPAN CLASS=HEADER>Tracking project issues</SPAN>
<P>
<SPAN CLASS="PlainText"><B>Project help for project owner administration: Index</B>
<P>

<UL>
<DL>
<DT><A HREF="ProjectOwnerAdmin.html">Project owner administration</A>
	<DD><A HREF="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</A>
	<DD><A HREF="ProjectOwnerNews.html">Managing project site news</A>
	<DD><A HREF="ProjectOwnerFiles.html">Managing project files</A>
	<DD><A HREF="ProjectOwnerMembers.html">Adding project members and approving roles</A>
	<DD><A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>
`	<dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a>
	<DD><A HREF="ProjectOwnerSource.html">Managing project source code</A>
	<DD><B>You are here: Tracking project issues
		<UL>
		<LI><A HREF="#adminpermissions">About administrative issue tracking permissions</A>
		<LI><A HREF="#adminconfigure">Configuring IssueZilla's administrative options</A>
		<LI><A HREF="#admintips">Tips and tricks for issue management</A>
		</UL></B>
<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
</DL>
</UL>


<P>
<B>Issue tracker tool documentation</B>
<UL>
	<DL>
	 <DT><A HREF="ProjectIssues.html">Project Issues page help</A>
     <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>
    </DL>
</UL>
<P>

<HR NOSHADE SIZE=1>
<A NAME="adminpermissions"><SPAN CLASS="InputHeader">Issue tracking administration</SPAN></A>
     <P>
     <P>Because you are a Project Owner, you automatically have administrative permissions in IssueZilla to manage and track your project's issues. You can access these administrative options two different ways:
	<UL>
	<LI>Your view of the <B>Project Issues</B> page includes additional sections to <I>Edit Users</I>, <I>Edit Groups</I>, and <I>Edit Components</I>.
	<P>
	<LI>All administrative options are included in the Issue Tracking toolbar, which appears in your view of all issue tracking screens.
	</UL>
<P>
Your role of Project Owner gives you the ability to configure almost every element of IssueZilla. Descriptions of these options and their default settings follows. Probably the most significant permission you have is the ability to edit the issue tracking permissions of all other users on your project. This can include delegating some of these administrative permissions to other users to help manage and plan the project workload.
     <P>
If one of your project members builds a solid track record of committing issues that get confirmed, this is probably a person who understands the project and the issue tracking system well enough to be granted the "Can confirm an issue" permission. As a project owner, you can and should use IssueZilla to track this kind of information about project participants to help you manage project issues effectively.
<P>
To learn how to assign issue tracking permissions to project members, see "Users" in the next section

<HR NOSHADE SIZE=1>
<A NAME="adminconfigure"></A><SPAN CLASS="InputHeader">Configuring IssueZilla's administrative options</SPAN>
<P>
<DL>
<DT><B>Prefs</B> (Preferences) <DD>Lets you configure some aspects of your issue tracking functionality and display environment, including:
<P>
	<UL>
	<LI>Email settings for automatic issue email notifications to you. 
    <LI>Page footer links to be included in your query results screens.
	<LI>Permissions assigned to you as the default issue tracking administrator. (You control these permissions for all members of your project through the <I>Users</I> option in the Issue Tracking toolbar.)
	</UL>
<P>
<DT><B>Sanity check</B> <DD> An automated process that checks for an identifies any anomalies in your project's issues database, such as conflicting dependencies, committed issue errors, and correct references between issue reporters and user profiles.
<P>
<DT><B>Users</B> <DD> A text string field lets you access the user edit screen either by filtering for specific users or leaving it blank to access the full list of users after clicking the "Submit" button. Clicking on listed user's link displays another edit screen where you can check and uncheck permissions options.
<P>
<DT><B>Components</B> <DD> A component selection screen that lets you create, define, edit, add, and delete project components and subcomponents. Clicking on a component link in the list displays another edit screen where you can configure that particular component or subcomponent.
<P>
<DT><B>Groups</B> <DD> A group selection screen that lets you create, define, and delete groups specifically for issue tracking purposes, and assign project member users to groups. You can make changes to one, several, or all fields and submit them all at once. Your project also includes a default set of groups pertaining to issue tracking permissions.
<P>
<DT><B>Keywords</B> <DD> A keyword selection screen that lets you create, define, edit, and delete regular expression keywords to be used for issue tracking groups and queries.
</DL>

<HR NOSHADE SIZE=1>
<A NAME="admintips"></A><SPAN CLASS="InputHeader">Tips and tricks for issue management</SPAN>
<P>
IssueZilla is a powerful tool for managing and tracking your project's development activities down to the fine-grained details. As with most tools, users develop inevitably develop shortcuts and tricks to compensate for particular aspects of the tool, or to tailor it to their specific needs. IssueZilla is no exception.
<P>
What follows is a sampling of several tricks that have proved particularly useful to project managers or users with administrative issue tracking permissions:
<UL>
<LI>Avoid configuring the same management-level queries repeatedly by creating permanently displayed links to information you use constantly. For example, you can create a page of links for each project member's issue list, and for regularly used milestone or issue status queries.
<P>
<LI>Because issues may not be deleted, you can create components or subcomponents named "issue graveyard" or "unknown" to collect dead or no longer applicable issues. IssueZilla's non-delete feature is actually a protective design feature since the ability to track such dead issues can sometimes come in handy, or at least preserve aspects of project history.
<P>
<LI>Create a "not determined" milestone for project issues not yet tied to any particular project milestone date or release. Development project objectives and priorities tend to shift dynamically. This lets you identify and hold in reserve those issues affected by your project's evolution.
<P>
<LI>Add a pseudo user known as "placeholder" (or some other equally obvious generic identity) who can "own" issues that you are not yet ready or able to assign to specific project members.
</UL>
<P>     

<HR NOSHADE SIZE=1>
<A HREF="ProjectOwnerAdmin.html">Back to Project Owner Administration help</A><BR>
<A HREF="/servlets/HelpTOC">Back to main Help index</A>
</SPAN>
</BODY>
</HTML>
@


1.6
log
@revising document index and links
@
text
@a7 2
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
d21 1
a105 2
</TR>
</TABLE>
@


1.5
log
@html edits; revised doc index
@
text
@d24 1
a24 1
	<DD><B>You are here: Tracking project issues</B>
d29 1
a29 1
		</UL>
d36 1
a36 1
<B>More help for issue tracking</B>
@


1.4
log
@added <title> tags to all files
@
text
@d12 1
a12 1
<SPAN CLASS="PlainText">Project help for project owner administration: Index
a86 1
<P>
@


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
d110 2
@


1.2
log
@updated for new help format
@
text
@d1 102
a102 102
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
<SPAN CLASS=HEADER>Tracking project issues</SPAN>
<P>
<SPAN CLASS="PlainText">Project help for project owner administration: Index
<P>

<UL>
<DL>
<DT><A HREF="ProjectOwnerAdmin.html">Project owner administration</A>
	<DD><A HREF="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</A>
	<DD><A HREF="ProjectOwnerNews.html">Managing project site news</A>
	<DD><A HREF="ProjectOwnerFiles.html">Managing project files</A>
	<DD><A HREF="ProjectOwnerMembers.html">Adding project members and approving roles</A>
	<DD><A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>
	<DD><A HREF="ProjectOwnerSource.html">Managing project source code</A>
	<DD><B>You are here: Tracking project issues</B>
		<UL>
		<LI><A HREF="#adminpermissions">About administrative issue tracking permissions</A>
		<LI><A HREF="#adminconfigure">Configuring IssueZilla's administrative options</A>
		<LI><A HREF="#admintips">Tips and tricks for issue management</A>
		</UL>
<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
</DL>
</UL>


<P>
<B>More help for issue tracking</B>
<UL>
	<DL>
	 <DT><A HREF="ProjectIssues.html">Project Issues page help</A>
     <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>
    </DL>
</UL>
<P>

<HR NOSHADE SIZE=1>
<A NAME="adminpermissions"><SPAN CLASS="InputHeader">Issue tracking administration</SPAN></A>
     <P>
     <P>Because you are a Project Owner, you automatically have administrative permissions in IssueZilla to manage and track your project's issues. You can access these administrative options two different ways:
	<UL>
	<LI>Your view of the <B>Project Issues</B> page includes additional sections to <I>Edit Users</I>, <I>Edit Groups</I>, and <I>Edit Components</I>.
	<P>
	<LI>All administrative options are included in the Issue Tracking toolbar, which appears in your view of all issue tracking screens.
	</UL>
<P>
Your role of Project Owner gives you the ability to configure almost every element of IssueZilla. Descriptions of these options and their default settings follows. Probably the most significant permission you have is the ability to edit the issue tracking permissions of all other users on your project. This can include delegating some of these administrative permissions to other users to help manage and plan the project workload.
     <P>
If one of your project members builds a solid track record of committing issues that get confirmed, this is probably a person who understands the project and the issue tracking system well enough to be granted the "Can confirm an issue" permission. As a project owner, you can and should use IssueZilla to track this kind of information about project participants to help you manage project issues effectively.
<P>
To learn how to assign issue tracking permissions to project members, see "Users" in the next section

<HR NOSHADE SIZE=1>
<A NAME="adminconfigure"></A><SPAN CLASS="InputHeader">Configuring IssueZilla's administrative options</SPAN>
<P>
<DL>
<DT><B>Prefs</B> (Preferences) <DD>Lets you configure some aspects of your issue tracking functionality and display environment, including:
<P>
	<UL>
	<LI>Email settings for automatic issue email notifications to you. 
    <LI>Page footer links to be included in your query results screens.
	<LI>Permissions assigned to you as the default issue tracking administrator. (You control these permissions for all members of your project through the <I>Users</I> option in the Issue Tracking toolbar.)
	</UL>
<P>
<DT><B>Sanity check</B> <DD> An automated process that checks for an identifies any anomalies in your project's issues database, such as conflicting dependencies, committed issue errors, and correct references between issue reporters and user profiles.
<P>
<DT><B>Users</B> <DD> A text string field lets you access the user edit screen either by filtering for specific users or leaving it blank to access the full list of users after clicking the "Submit" button. Clicking on listed user's link displays another edit screen where you can check and uncheck permissions options.
<P>
<DT><B>Components</B> <DD> A component selection screen that lets you create, define, edit, add, and delete project components and subcomponents. Clicking on a component link in the list displays another edit screen where you can configure that particular component or subcomponent.
<P>
<DT><B>Groups</B> <DD> A group selection screen that lets you create, define, and delete groups specifically for issue tracking purposes, and assign project member users to groups. You can make changes to one, several, or all fields and submit them all at once. Your project also includes a default set of groups pertaining to issue tracking permissions.
<P>
<DT><B>Keywords</B> <DD> A keyword selection screen that lets you create, define, edit, and delete regular expression keywords to be used for issue tracking groups and queries.
</DL>

<HR NOSHADE SIZE=1>
<P>
<A NAME="admintips"></A><SPAN CLASS="InputHeader">Tips and tricks for issue management</SPAN>
<P>
IssueZilla is a powerful tool for managing and tracking your project's development activities down to the fine-grained details. As with most tools, users develop inevitably develop shortcuts and tricks to compensate for particular aspects of the tool, or to tailor it to their specific needs. IssueZilla is no exception.
<P>
What follows is a sampling of several tricks that have proved particularly useful to project managers or users with administrative issue tracking permissions:
<UL>
<LI>Avoid configuring the same management-level queries repeatedly by creating permanently displayed links to information you use constantly. For example, you can create a page of links for each project member's issue list, and for regularly used milestone or issue status queries.
<P>
<LI>Because issues may not be deleted, you can create components or subcomponents named "issue graveyard" or "unknown" to collect dead or no longer applicable issues. IssueZilla's non-delete feature is actually a protective design feature since the ability to track such dead issues can sometimes come in handy, or at least preserve aspects of project history.
<P>
<LI>Create a "not determined" milestone for project issues not yet tied to any particular project milestone date or release. Development project objectives and priorities tend to shift dynamically. This lets you identify and hold in reserve those issues affected by your project's evolution.
<P>
<LI>Add a pseudo user known as "placeholder" (or some other equally obvious generic identity) who can "own" issues that you are not yet ready or able to assign to specific project members.
</UL>
<P>     

<HR NOSHADE SIZE=1>
<A HREF="ProjectOwnerAdmin.html">Back to Project Owner Administration help</A><BR>
<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
@d3 4
a6 1
  
a7 2
<SPAN class=Header>Tracking and managing project issues</SPAN>
<span class="PlainText">
d9 16
a24 5
	<DL>
	<DT><A HREF="#adminpermissions">About administrative issue tracking permissions</a>
	<DT><A HREF="#adminconfigure">Configuring IssueZilla's administrative options</A>
	<DT><A HREF="#admintips">Tips and tricks for issue management</A>
	</DL>
d26 2
d29 1
a29 1
<B>Other help for issue tracking</B>
d36 1
a36 2
     <DT><A HREF="#Moreinfo">More resources about issues and issue tracking</A> 
	 </DL>
d40 2
a41 2
<HR noShade SIZE=1>
<A NAME="adminpermissions"><span class="InputHeader">Issue tracking administration</span></A>
d43 1
a43 1
     <p>Because you are a Project Owner, you automatically have administrative permissions in IssueZilla to manage and track your project's issues. You can access these administrative options two different ways:
d51 1
a51 1
     <p>
d56 2
a57 2
<HR noShade SIZE=1>
<A NAME="adminconfigure"></A><span class="InputHeader">Configuring IssueZilla's administrative options</SPAN>
d74 1
a74 1
<DT><B>Groups</B> <DD> A group selection screen that lets you create, define, edit, and delete groups specifically for issue tracking purposes, and assign project member users to groups. You can make changes to one, several, or all fields and submit them all at once. Your project also includes a default set of groups pertaining to issue tracking permissions.
d79 1
a79 1
<HR noShade SIZE=1>
d81 1
a81 1
<A NAME="admintips"></A><span class="InputHeader">Tips and tricks for issue management</SPAN>
d97 1
a97 1
<HR noShade SIZE=1>
d99 1
a99 1
<a href="Help.html">Back to main Help index</a></p></span>
@

