Differences between revisions 1 and 42 (spanning 41 versions)
⇤ ← Revision 1 as of 2008-12-17 10:49:05 →
Size: 1304
Editor: EldZierau
Comment:
← Revision 42 as of 2010-08-16 10:24:57 → ⇥
Size: 3460
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Creation of a Tracker Issue ==
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. 		## page was renamed from Process/Create Tracker Issue
~-<<Action(edit)>>-~
Line 4: Line 4:
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. The Creation of a Tracker Issue process contains [[#CreateTIDescription|Description]], [[#CreateTIPurpose|Purpose]], [[#CreateTIResponsible|Responsible]], [[#CreateTIthod|Method]], [[#CreateTITime|Time]], [[#CreateTIInput|Input]] and [[#CreateTIOutput|Output]].
Line 6: Line 6:
Please remmember ALWAYS to:
 * For bugs: [[BR]] Please Add log files under field "Attach Files:" if you describe an error that can be traced in log files (see below).
 * In case you are not a user: [[BR]] Please write who you are.		 <<Anchor(CreateTIDescription)>>
'''~+Description+~'''<<BR>>
Anyone with access to the internet can create a Tracker Issue in form of a Bug, a Feature Request or a Patch.
Line 10: Line 10:
=== 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.		 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.
Line 13: Line 12:
include logs (examples from new deploy) <<Anchor(CreateTIPurpose)>>
'''~+Purpose+~'''<<BR>>
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.
Line 15: Line 16:
... <to be written> <<Anchor(CreateTIResponsible)>>
'''~+Responsible+~'''<<BR>>
Anybody
Line 17: Line 20:
=== 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.		 <<Anchor(CreateTIMethod)>>
'''~+Method+~'''<<BR>>
 * 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'
Line 20: Line 36:
=== Creation of a Patch ===
Choose the Patch Tracker in case you want to report a patch to inclusions in !NetarchiveSuite. 		<<Anchor(CreateTITime)>>
'''~+Time+~'''<<BR>>
Any time
Line 23: Line 40:
... <to be written> <<Anchor(CreateTIInput)>>
'''~+Input+~'''<<BR>>
Any issue to be reported as a bug, a feature request of a patch.

<<Anchor(CreateTIOutput)>>
'''~+Output+~'''<<BR>>
A '''new''' Tracker issue registered in the !NetarchiveSuite GForge tracker system.

edit

The 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:

    • Summary

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

    • Version

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

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