Overview
Project DiaStar uses the Mantis Bug Tracking system <http://www.mantisbt.org/>.
The following provides an overview of its usage and should be read prior to using the bug tracking system.
User Roles
A user property, controlling what the user is allowed to view and modify, as well as the complexity of the interface. The access levels are:
- viewer: allowed to view but not modify issues.
- reporter: same as viewer, plus the ability to create new issues.
- updater: same as reporter, plus the ability to update issue.
- developer: same as updater, plus the ability to modify the status of issues.
- manager: same as developer, the manager has full issue management ability
- administrator: same as manager, plus the ability to fully manage the the bug tracker configuration.
Issue Reporting
Here are the fields that must be filled out when a bug is entered:
Project
DiaStar uses a single bug tracking system for all of its projects. The active projects currently are
- DiaStar server
- chan_woomera
This should be set in the drop-down list in the upper right-had corner of the screen.
Category
This field is currently unused and each issue should be assigned to the "Default" category.
Reproducibility
An issue property, giving how often the issue has been seen when trying to reproduce it. Specified by the reporter that created the issue, but may be changed later. Possible values are:
- always: the issue can be reproduced every time.
- sometimes: occasional issue that should be reproducible.
- random: intermittent issue that is hard to reproduce.
- unable to reproduce: the issue only occurred once and cannot be reproduced.
- have not tried: no attempt has been made to reproduce the issue.
- N/A:
Severity
The severity determines how bad the effects of the issue are. The severity assigned when the issue is created may be changed at a later time.
Possible values are:
- Feature: the issue is not a problem, but is a request for a change in functionality or request for additional functionality.
- Text: text is incorrect
- Minor: not trivial, but there is a workaround
- Major: there is no workaround
- Crash: product crashes
- Block: prevents operating or testing part of system
Summary
A short, one-line summary of the issue.
Description
A full description of the issue.
Issue Management
Here are the non-obvious fields that are seen when an existing bug is viewed:
Priority
An issue property, giving the importance of addressing the issue. Specified by the reporter that created the issue, but may be changed later.
Possible values are:
- None
- Low
- Normal
- High
- Urgent
- Immediate
Status
The current status of an issue.
Possible values are:
- new: issue has not been acted upon or been assigned to anybody
- acknowledged: the issue has been reviewed, but no further action has been taken.
- confirmed: the issue has been reproduced but not yet assigned to a developer.
- assigned: the issue is being worked on by a developer.
- resolved: the issue has been fixed by development and is awaiting confirmation from the reporter prior to closing.The resolution field must be set
- closed: the issue is closed and no further action should be taken on the issue without reopening it. The resolution field must be set
- feedback: catch-all disruption in the issue life-cycle
Resolution
The resolution field is used to categorize how an issue was fixed. The resolution should be completed as the issue moves to a status of "resolved" or "closed".
Possible values are:
- open
- fixed
- reopened (The issue status had previously been "resolved" or "closed", however the issue is no being re-evaluated)
- duplicate*
- works for me: developer couldn't duplicate reported defect*
- not a problem: product is best without issue being fixed*
- suspended: will not fix now, but may re-evaluate later*
- won't fix: will not fix for other reasons (e.g. too much work compared to benefit, would cause other problems)
- not fixable: It is not possible to fix this issue*
Note:
If an issue is marked with a severity of "feature". The resolution of "fixed" indicates the the feature request has been implemented.
REFERENCES
