Differences between revisions 33 and 35 (spanning 2 versions)
Revision 33 as of 2009-01-19 15:15:34
Size: 3969
Editor: EldZierau
Comment:
Revision 35 as of 2009-01-20 10:03:07
Size: 3421
Editor: EldZierau
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
It is important to give enough information when the tracker issue is created. Especially for person who does not have a user account, it 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.

Please remember ALWAYS to:
 * For bugs: [[BR]] Add log files under 'Attach Files' field, in case you describe an error that can be traced in log files (see below).
 * For bugs: [[BR]] Make a remark of version in the 'Summary' field, in case the version is not listed in possible values for the 'Version' field.
 * For non-registered users: [[BR]] Write who you are in the 'Summary' field.
It is important to give enough information when the tracker issue is created. Especially for person who does not have a user account, it 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. Furthermore it is important to give information of version, that a bug appears in or patch files will work in, - and for bugs also give log-files in order for the developers to evaluate the bug.
Line 26: Line 21:
 * Classify your issue, i.e. find the [:BugInfGuide/Fields#FieldDataType:'Data Type'] of your Tracker (bug, feature request or patch, see [:BugInfGuide/Fields#FieldDataType:'Data Type'] for further description)
   * a '''bug''', if the issue is concerned with an error in the !NetarchiveSuite package, e.g. a spelling error
   * a '''feature request''', if the issue represents a suggested change in the !NetarchiveSuite package, e.g. a better interface
   * a '''patch''', in case it includes explicit changes and/or additions to the !NetarchiveSuite package, e.g. new translation files.
 * Classify your issueas a bg, feature request or a patch, i.e. find the [:BugInfGuide/Fields#FieldDataType:'Data Type'] of your Tracker (bug, feature request or patch, see [:BugInfGuide/Fields#FieldDataType:'Data Type'] for further description)

Action(edit)

The Creation of a Tracker Issue process contains [#CreateTIDescription Description], [#CreateTIPurpose Purpose], [#CreateTIResponsible Responsible], [#CreateTIthod Method], [#CreateTITime Time], [#CreateTIInput Input] and [#CreateTIOutput Output].

Anchor(CreateTIDescription) DescriptionBR 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. Especially for person who does not have a user account, it 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. Furthermore it is important to give information of version, that a bug appears in or patch files will work in, - and for bugs also give log-files in order for the developers to evaluate the bug.

Anchor(CreateTIPurpose) PurposeBR 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.

Anchor(CreateTIResponsible) ResponsibleBR Anybody

Anchor(CreateTIMethod) MethodBR

Anchor(CreateTITime) TimeBR Any time

Anchor(CreateTIInput) InputBR Any issue to be reported as a bug, a feature request of a patch.

Anchor(CreateTIOutput) OutputBR A new Tracker issue registered in the NetarchiveSuite GForge tracker system.

Process/Create Tracker Issue WithoutTitle (last edited 2010-08-16 10:24:57 by localhost)