Changes between Version 9 and Version 10 of ReportBug


Ignore:
Timestamp:
Feb 1, 2013 6:43:24 PM (5 years ago)
Author:
abeccati
Comment:

guidance on ticket fields

Legend:

Unmodified
Added
Removed
Modified
  • ReportBug

    v9 v10  
    1515    * '''Make sure the data you entered is correct'''
    1616
    17       Please doublecheck your input to make sure that all the information regarding component, milestone etc is correct. Also try to provide keywords if you can.
     17      Please doublecheck your input to make sure that all the information regarding component, milestone etc is correct. Also try to provide keywords if you can. Here is some advice:
     18      * component: if unsure ask on the dev list or pick the most likely one (the component owner will redirect it if needed)
     19      * milestone: leave it empty unless you are contributing to a milestone release preparation
     20      * priority: tickets are usually addressed by their priority, Major is the default, Blocker is for mission critical issues impeding use of the system where no workaround exists while Trivial is for annoyances or polishing tasks
     21      * Type
     22        * Defect: If something is not working as expected or there is incorrect documentation
     23        * Feature: If you are proposing an entirely new feature for the system or to define high-level features for milestones
     24        * Enhancement: If you are proposing an improvement or addition to an existing feature
     25        * Task: Is reserved for activities to be performed which do not fit in the above categories
    1826
    1927    * '''Give good description of the problem'''
    2028
    21       This also includes the necessary steps to reproduce the problem!
     29      This also includes the necessary steps to reproduce the problem! Ideally, provide a failing systemtest attached to the ticket for Critical or Blocker defects
    2230
    2331    * '''If you have a solution - tell us! '''