Version 9 (modified by cpinkham, 16 years ago) (diff)


We eventually look at all tickets. But if you go through this quick checklist before submitting the ticket, it will be addressed more quickly.

First, please verify that:

  • Your bug doesn't already have a ticket (report:6)
  • That your bug is not already fixed in current SVN
  • That this is really a bug, and not a feature request. Feature requests go in either the old wiki or the new wiki.

If this is a compiling problem, e-mail the users list, then the developer list before adding a ticket. These are often caused by toolchain or dependency problems. Of course, if the problem is only present after a particular recent commit, e-mail the developer list immediately.

Once you've decided to create that ticket:

  • Make sure to assign it to the GoToDev for the broken component.
  • Make sure you attach logs, patches, and backtraces after you create the ticket.
  • If problem causes a SEGFAULT, attach the backtrace to the ticket.
  • If you submit a patch, make sure it adheres to the MythTV coding standards.
  • Please do not increase 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.

PS To attach a patch or a backtrace, you must first create a ticket, and then there will be an 'Attach File' button when you view the new ticket. Attach logs as either plaintext or compressed files, please do not attach non-plaintext files such as OpenOffice?, Word, or RTF documents.

If 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.