Differences between revisions 34 and 42 (spanning 8 versions)
⇤ ← Revision 34 as of 2009-01-20 10:02:13 →
Size: 3767
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. 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. 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:
[[Anchor(CreateTIPurpose)]]
'''~+Purpose+~'''[[BR]]		 <<Anchor(CreateTIPurpose)>>
'''~+Purpose+~'''<<BR>>
Line 15: Line 16:
[[Anchor(CreateTIResponsible)]]
'''~+Responsible+~'''[[BR]]		 <<Anchor(CreateTIResponsible)>>
'''~+Responsible+~'''<<BR>>
Line 19: Line 20:
[[Anchor(CreateTIMethod)]]
'''~+Method+~'''[[BR]]
 * 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.
 * 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 29: 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
     * 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 patch, files with updates/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.		      * 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.
Line 38: Line 36:
[[Anchor(CreateTITime)]]
'''~+Time+~'''[[BR]]		 <<Anchor(CreateTITime)>>
'''~+Time+~'''<<BR>>
Line 42: Line 40:
[[Anchor(CreateTIInput)]]
'''~+Input+~'''[[BR]]		 <<Anchor(CreateTIInput)>>
'''~+Input+~'''<<BR>>
Line 46: 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)