> For the complete documentation index, see [llms.txt](https://handbook.musescore.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.musescore.org/3/support/bug-reports-and-feature-requests.md). # Bug reports and Feature requests **The musescore.org issue tracker has been retired on March 2023, please report bugs on GitHub instead:**\ ## Forum, musescore.org issue tracker and github.com issue tracker **Before filing bug reports or feature requests in the Issue Tracker, it is recommended first to** [**search for similar ones**](node:309537,fragment="Check-if-the-bug-is-known")**, post in the relevant** [**Forum**](https://musescore.org/forum) **if none is found**, so others may help establish a bug as genuine, provide ideas and second opinions for new features, and gather concensus.\ Include a link to such discussion when creating the Issue in Issue Tracker.\ The role of [Issue Tracker on musescore.org](https://musescore.org/project/issues) is to triage before opening an [issue on github](https://github.com/musescore/MuseScore/issues). The expectancy is that the .org tracker will at some point undergo some changes to facilitate it linking to github issues, [source](https://musescore.org/en/4.0#comment-1153440).\ Once the issue is referred/reposted to github, the [one on musescore.org will be marked Duplicate](https://musescore.org/en/node/338522#comment-1158083) to unclutter the triage system. ## Bug reports * Try to reproduce the issue with [the latest nightly](https://musescore.org/download#Development-builds). You may also view the [version history](https://github.com/musescore/MuseScore/commits/master) to check whether it has been fixed/implemented already. * Please include as much of the following information as you know and limit each issue to one report: * Version/revision of MuseScore you are using (e.g. version 3.0, revision [871c8ce](https://github.com/musescore/musescore/commit/871c8ce)). Check **Help -> About...** (Mac: **MuseScore -> About MuseScore...**). * Operating system being used (e.g. Windows 10, macOS 10.15 or Ubuntu 20.04) * Describe the precise steps that lead to the problem (where do you click, what keys do you press, what do you see, etc.).\ If you are not able to reproduce the problem with the steps, it is probably not worth reporting it as the developers will not be able to reproduce (and solve) it either. Remember that the goal of a bug report is not only to show the problem, but to allow others to reproduce it easily. * Attach the score that shows the problem, at least a minimal example —use the "File attachments" option at the bottom of the page, just above the **Save** and **Preview** buttons when you're typing your post. * Fill in the correct [issue detail field](https://musescore.org/en/node/309537#Issue-details), eg If you did not gather any shared experience in forum, use **Frequency: Once**. Once the issue is referred/reposted to github, the one on musescore.org will be marked Duplicate to unclutter the triage system, jump to [triage](#forum-musescoreorg-issue-tracker-and-githubcom-issue-tracker) above. ## Feature requests * Be brief, but describe the goal as precisely as you can * Describe the context in which the new feature is intended to work * Suggest a specific workflow, if you can ## Cross linking issues When you write a comment in a forum topic, you can refer to an issue in the issue tracker using the following notation: ´\[#number]´\ That way the link in the comment will include the issue title and reflect the current status of the issue. Furthermore, it'll lead to the forum topic being listed in the issue itself.\ Type \[#153286] get [#153286: Change instrument causes a crash](https://musescore.org/en/node/153286) ## External links * [How to write a good bug report: step-by-step instructions](https://musescore.org/en/node/309537) (MuseScore HowTo) * [How to attach a file](https://musescore.org/en/node/289899) (MuseScore HowTo) * [Compose tips](https://musescore.org/filter/tips) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://handbook.musescore.org/3/support/bug-reports-and-feature-requests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.