NetarchiveSuiteThe Creation of a Tracker Issue process contains Description, Purpose, Responsible, Method, Time, Input and Output.
Description
Anyone with access to the internet can create a Tracker Issue in form of a Bug, a Feature Request or a Patch.
It is important to give enough information when the tracker issue is created. Some information is hard to complement a Tracker Issue later. This is due to the way that GForge works, and therefore not in our power to change.
Purpose
To make a formal report of a tracker issue (bug, feature request or patch) in a way that enables tracking of the life-cycle of the issue.
Responsible
Anybody
Method
Classify your issueas a bg, feature request or a patch, i.e. find the 'Data Type' of your Tracker (bug, feature request or patch, see 'Data Type' for further description)
Go to tracker issue in NetarchiveSuite GForge matching your issue classification (bugs, feature request, patch) and click 'Submit New'.
Fill in the fields (described under Fields for different Tracker Issues marked with "new").
Most importantly are the fields:- remember to include name of reporting person, in case you are not a user in the system.
remember to include version, if it does not exist in the drop down list for the 'Version'
Attach Files - where
in case of a bug, logs must be attached (please refer to Hints to Where to Find Log-files)
If you forgot to attach files at creation, it is only possible for internal users to attached them afterwards. External users will have to send them to the developer group via mail.- in case of a patch, files with diffs/additions must be attached
If known it is desireble if the fields 'Assigned To', 'Module' are set.
Fileds like 'Priority', 'Status' and 'Duplicate Of' will rarely be set at creation time.- Click 'Submit New'
Time
Any time
Input
Any issue to be reported as a bug, a feature request of a patch.
Output
A new Tracker issue registered in the NetarchiveSuite GForge tracker system.