Action(edit)

The Creation of a Tracker Issue process contains [#Description Description], [#Purpose Purpose], [#Responsible Responsible], [#Method Method], [#Time Time], [#Input Input] and [#Output Output].

Anchor(Description) DescriptionBR Any one with access to the internet can in princip create an Issue Tracker 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 that do not have a user account, it is hard to complement a Issue Tracker later. This is due to the way that GForge works, and therefore not in our power to change.

Please remmember ALWAYS to:

• For bugs: BR Please 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 If the version is not lsted in possible values for the 'Version' field, please make a remark in the 'Summary' field.

• In case you are not a user: BR Please write who you are in the 'Summary' field.

Anchor(Purpose) PurposeBR

Creation of a Bug

Choose the Bug Tracker in case you want to report a bug which should be implemented as a fix in NetarchiveSuite.

include logs (examples from new deploy)

... <to be written>

Creation of a Feature Request

Choose the Feature Request Tracker in case you want to report a feature request which you would like to have implemented in NetarchiveSuite. The rest of the process is the same as for Bugs, please refer to the Reporting a Bug section.

Creation of a Patch Choose the Patch Tracker in case you want to report a patch to inclusions in NetarchiveSuite.

... <to be written>