Changes between Version 3 and Version 4 of TicketHowTo


Ignore:
Timestamp:
Oct 25, 2005, 9:00:41 PM (14 years ago)
Author:
Isaac Richards
Comment:

Adding note about not changing the priority/severity/milestone.

Legend:

Unmodified
Added
Removed
Modified
  • TicketHowTo

    v3 v4  
    1414 * If problem causes a SEGFAULT, attach the [http://www.mythtv.org/docs/mythtv-HOWTO-21.html#ss21.2 backtrace] to the ticket.
    1515 * If you submit a patch, make sure it adheres to the [http://www.mythtv.info/moin.cgi/CodingStandards MythTV coding standards].
     16 * Please do '''not''' change a ticket's priority, severity, or milestone from the defaults.  These fields are for the person who is fixing the issue to decide.  Don't change these after the ticket's been filed, either - they'll likely just get changed back.
    1617
    1718Tickets are generally not addressed as quickly as e-mails to the developer list, but they ensure that the problem doesn't get completely lost in the noise.
    1819
    1920If your ticket gets marked as worksforme or invalid consider this a challenge to improve the bug report. Problems often only occur with a particular setting or with some particular hardware. Figuring out what exactly is causing the problem will make it possible to reproduce the bug, which is the first step in fixing it. If the ticket is marked as invalid rather than worksforme, it probably failed some check on this checklist. Also, don't get into an arguement with whoever closed your ticket. Remember, since this person reviewed your ticket, this is the person most likely to fix your problem.
     21