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


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

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

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

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

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

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


desc
@@


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

<TITLE>Getting Started with IssueZilla</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Getting started with IssueZilla</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
     <P>
     <A HREF="#useraccounts">User accounts</A><BR>
     <A HREF="#permissions">About permissions</A><BR>
     <A HREF="#adminpermissions">Admin setup</A><BR>
     <P>
     <A NAME="useraccounts"><span class="InputHeader">User Accounts</span></A><P>

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

     <p>Information about your account is available under "Edit prefs"
     in the IssueZilla toolbar. You have several options to change how
     your account is configured.
     <p>
     <DL>
      <DT><span class="InputHeader">Account settings</span>
       <DD>Contains username and password information
      <DT><span class="InputHeader">Email settings</span> 
       <DD>Controls your automatic email notification settings. 
      <DT><span class="InputHeader">Page footers</span> 
       <DD>Include/exclude "My issues" or your named, custom queries in every IssueZilla page footer.
    </DL>
     <p>
     You can also view a list of IssueZilla permissions assigned to you.
     <p>
     <A NAME="permissions"><span class="InputHeader">About 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 your permissions using the "Edit prefs" link in the
     IssueZilla tool bar. Your 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 are a project owner, you are an administrative level
IssueZilla user who can assign permissions to other project
members. (See more about <A NAME="adminpermissions">administrative
permissions</A> below.)

</UL>

Whatever your role in a project, if you really feel that you ought to
have additional IssueZilla permissions, the project owner is the right
person to ask (via private email, please!). You may need to request a
new 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="/docs/issue_lifecycle.html">lifecycle of an issue</A>.

     <p>
     <A NAME="adminpermissions"><span class="InputHeader">Admin Setup</span></A>
     <P>

     <p>If you are a project owner, you automatically have
     administrative permissions in IssueZilla to manage and track your
     project's issues. Admin options appearing in the IssueZilla tool
     bar allow you to:
     <p>
     <UL>
      <LI>modify IssueZilla's overall configuration for your project, including adding custom pages
      <LI>conduct "sanity checks" to identify any anomalies in your project's issues database
      <LI>enter and modify project components
      <LI>edit user information and privileges
      <LI>define groups and assign users to groups
     </UL>
     <p>Probably the most significant permission you have as a project
     owner is the ability to edit the permissions of all other users
     on your project. This can include giving other users
     administrative permissions to delegate some of your issue
     management workload.
     <p>
     If a project member has submitted several issues that get
     confirmed, then this is probably a person who understands the
     project and the issue tracking system well, and deserves the "Can
     confirm an issue" permission. As a project owner, you should
     track this and proactively manage user permissions assignments
     accordingly.
    </TD>
  </TR>
</TABLE>



</BODY>
</HTML>
@


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


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


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

<TITLE>Getting Started with IssueZilla</TITLE>

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


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

<TITLE>Getting Started with IssueZilla</TITLE>

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


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

