Changes between Version 10 and Version 11 of ReportBug


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

search added

Legend:

Unmodified
Added
Removed
Modified
  • ReportBug

    v10 v11  
    1111    * '''Make sure the ticket has not already been submitted.'''
    1212
    13       Click on [/report View Tickets] and then [/report/6 All Tickets By Milestone (Including closed)] to verify that your issue or feature request is not already in the database. Please also check if the issue or request is among the closed tickets, maybe it is not bug or has already been fixed/implemented in a newer version or the [/browser repository].
     13      Use the [/search search] feature on tickets, click on [/report View Tickets] and then [/report/6 All Tickets By Milestone (Including closed)] to verify that your issue or feature request is not already in the database. Please also check if the issue or request is among the closed tickets, maybe it is not bug or has already been fixed/implemented in a newer version or the [/browser repository].
    1414
    1515    * '''Make sure the data you entered is correct'''
    1616
    1717      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
     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
    2626
    2727    * '''Give good description of the problem'''