Project Issues

Project resources for project members: Index

Project resources for members

Project Home Page

Project News

Project Download

Project Members

Project Mailing Lists

Project Documentation

Project Source Code

You are here: Project Issues

• Accessing project issues
• About the IssueZilla tool
• Setting your issue tracking user preferences
• About your issue tracking permissions

Back to main Help index

More help on issue tracking

Entering and modifying issues

Querying and tracking issues

Generating status reports about project issues

More how-to information about issues and issue tracking

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

1. Ability to chart the progress of individuals and the overall project
2. Tracking and maintainance of project history
3. Generation and reporting of ongoing to-do lists for all project members.

The different sections appearing in the Project Issues page indicate the following issue tracking options available to you:

Query Database of Issues

Search project issues by number, keywords, assignee, or other criteria.

Enter An Issue

Write and commit an issue report to the database.

My Issues

View a list of project issues assigned to you.

My Preferences

Configure your issue tracker user settings.

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:

• Defects (a.k.a. "bugs")
• Enhancements
• Features
• Tasks
• Patches

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.

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.

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.

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

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

Email settings

Controls your automatic email notification settings.

Page footer

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

Permissions

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

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  My Preferences link on the Project Issues page, or the Edit Prefs link in the Issue Tracking toolbar.

Issue tracking permissions depend upon project role: 

• Observers can create and modify issues, but can make changes to only their own issues. Observers have the ability to comment on any issue. 

• 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.

• 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.

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 UNCONFIRMED issue to NEW . 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 lifecycle of issues.

• The issue life cycle
• Issue writing guidelines
• IssueZilla tips and tricks
• Contributing patches
• BugZilla FAQ**
• Step-by-step help for bug entry**
• BugZilla guide to writing good bug reports**
• Scarab, an open source issue tracking development project

** 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 Mozilla.org.

If you are interested in finding out about other bug tracking systems being developed, see the scarab open source project.

A note about IssueZilla and cookies : 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.