Differences between revisions 39 and 40
⇤ ← Revision 39 as of 2009-02-02 12:33:54 →
Size: 3181
Editor: EldZierau
Comment:
← Revision 40 as of 2009-02-27 10:40:29 → ⇥
Size: 3370
Editor: EldZierau
Comment:
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
     * in case of a bug, logs must be attached (please refer to [:Guidelines/LogFileHints:Hints to Where to Find Log-files])      * in case of a bug, logs must be attached (please refer to [:Guidelines/LogFileHints:Hints to Where to Find Log-files]) [[BR]] 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.

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

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

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

  • Go to tracker issue in NetarchiveSuite GForge matching your issue classification ([http://gforge.statsbiblioteket.dk/tracker/?atid=105&group_id=7&func=browse bugs], [http://gforge.statsbiblioteket.dk/tracker/?atid=108&group_id=7&func=browse feature request], [https://gforge.statsbiblioteket.dk/tracker/?atid=107&group_id=7&func=browse patch]) and click 'Submit New'.

  • Fill in the fields (described under [http://netarchive.dk/suite/BugInfGuide/Fields Fields for different Tracker Issues] marked with "new"). BR Most importantly are the fields:

    • [:BugInfGuide/Fields#FieldSummary:Summary]

    • [:BugInfGuide/Fields#FieldDetailedDescription:Detailed description]:

      • 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 [:BugInfGuide/Fields#FieldVersion:'Version']

    • [:BugInfGuide/Fields#FieldAttachFiles:Attach Files] - where

      • in case of a bug, logs must be attached (please refer to [:Guidelines/LogFileHints:Hints to Where to Find Log-files]) BR 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

    • [:BugInfGuide/Fields#FieldVersion:Version]

  • If known it is desireble if the fields [:BugInfGuide/Fields#FieldAssignedTo:'Assigned To'], [:BugInfGuide/Fields#FieldModule:'Module'] are set. BR Fileds like [:BugInfGuide/Fields#FieldPriority:'Priority'], [:BugInfGuide/Fields#FieldStatus:'Status'] and [:BugInfGuide/Fields#FieldDuplicateOf:'Duplicate Of'] will rarely be set at creation time.

  • Click 'Submit New'

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)