How to report a bug

• Apr 18, 2009 - 02:54

I still don't understand how to register a bug, and when I go to the url for information on this, I find it incomplete.

Thanks David for registering the difficulties I've had with this software, but it would be quicker if I could register them.

Regards,
:-}}

Comments

• Apr 18, 2009 - 06:13

The issue tracker is mostly for keeping track of bugs that people report on the forum (or testers discover on their own). I prefer that the bug is well tested (by the reporter) before it listed in the issue tracker so that the list of steps to reproduce the bug is concise and 100% reproducible. The goal is to make it as easy as possible for others to reproduce the problem so that they can confirm that the problem exists and check that it was properly fixed afterwards. It is often helpful to include a sample MuseScore file if it saves people a few manual steps or a picture if helps people better understand the problem.

Generally it is best to limit each bug report in the tracker to one bug. If a bug report lists multiple bugs it is difficult to mark the bug report as fixed or not fixed as development progresses.

A format that works well for most bugs is as follows:

  1. List the series of steps needed to reproduce the problem
  2. Describe the behavior you expect to happen
  3. Describe the actual behavior that happens
  4. State the version of MuseScore that you are using, and the operating system you are running it on

Reply

• Mar 16, 2015 - 15:17

Would you please provide a link here to the bug tracking system, including how we can see previously registered bugs. Because I don't even know where it is. And I have reported a number of bugs in the forums here and there but it doesn't seem to be very systematic and I have googled bug report MuseScore beta 2.....

Reply

Do you still have an unanswered question? Please log in first to post your question.