Differences between revisions 27 and 42 (spanning 15 versions)
⇤ ← Revision 27 as of 2009-01-19 14:39:38 →
Size: 3768
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:
~-[[Action(edit)]]-~ ## page was renamed from Process/Create Tracker Issue
~-<<Action(edit)>>-~
Line 3: Line 4:
The Creation of a Tracker Issue process contains [#CreateTIDescription Description], [#CreateTIPurpose Purpose], [#CreateTIResponsible Responsible], [#CreateTIthod Method], [#CreateTITime Time], [#CreateTIInput Input] and [#CreateTIOutput Output]. The Creation of a Tracker Issue process contains [[#CreateTIDescription|Description]], [[#CreateTIPurpose|Purpose]], [[#CreateTIResponsible|Responsible]], [[#CreateTIthod|Method]], [[#CreateTITime|Time]], [[#CreateTIInput|Input]] and [[#CreateTIOutput|Output]].
Line 5: Line 6:
[[Anchor(CreateTIDescription)]]
'''~+Description+~'''[[BR]]		 <<Anchor(CreateTIDescription)>>
'''~+Description+~'''<<BR>>
Line 9: Line 10:
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. 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 11: Line 12:
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.

[[Anchor(CreateTIPurpose)]]
'''~+Purpose+~'''[[BR]]		 <<Anchor(CreateTIPurpose)>>
'''~+Purpose+~'''<<BR>>
Line 20: Line 16:
[[Anchor(CreateTIResponsible)]]
'''~+Responsible+~'''[[BR]]		 <<Anchor(CreateTIResponsible)>>
'''~+Responsible+~'''<<BR>>
Line 24: Line 20:
[[Anchor(CreateTIMethod)]]
'''~+Method+~'''[[BR]]
 * Classify your issue as a bug, feature request or a patch 
   * 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.
 * 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]		 <<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]]:
Line 34: Line 28:
     * remember to include version, if it does not exist in the drop down list for the [:BugInfGuide/Fields#FieldVersion:'Version'] field
   * [:BugInfGuide/Fields#FieldDetailedDescription:Detailed description]:
   * [:BugInfGuide/Fields#FieldAttachFiles:Attach Files] - where
     * logs must be attached in case of a bug
     * files with updates/additions must be attached in case of a patch
   * [: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.		      * 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 42: Line 36:
'''''Include logs (examples from new deploy)'''''

[[Anchor(CreateTITime)]]
'''~+Time+~'''[[BR]]		 <<Anchor(CreateTITime)>>
'''~+Time+~'''<<BR>>
Line 48: Line 40:
[[Anchor(CreateTIInput)]]
'''~+Input+~'''[[BR]]		 <<Anchor(CreateTIInput)>>
'''~+Input+~'''<<BR>>
Line 52: Line 44:
[[Anchor(CreateTIOutput)]]
'''~+Output+~'''[[BR]]		 <<Anchor(CreateTIOutput)>>
'''~+Output+~'''<<BR>>

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)