musescore / musescore/MuseScore

Changing bracket type does not work

Open
#29,131 1 comment 1 reaction 2 assignees View on GitHub

@Eism is already working on this.

Since Aug 8, 2025.

P2 regression MS4 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Changing the bracket type on the help page does not work.

reproduce:

  1. create a new score (such as a grand staff)
  2. select the bracket
  3. click on the bracket from the "Brackets" palette.

actual behavior: unchanged
expect behavior: bracket type changed

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/bb11d7bb-2d42-4414-ba1b-e1aa2d07b327

What is the latest version of MuseScore Studio where this issue is present?

4.5.2.251141402

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 11 24H2

Additional context

In MuseScore 3, some symbols, such as brackets, keys, and beats, can be directly dragged onto existing symbols in the score table. However, it seems that some symbols in MuseScore 4 cannot be dragged in this way (they can only be dragged onto bars), and need to be selected first and then clicked to change.

https://github.com/user-attachments/assets/dd4dff55-d586-42b8-83f6-fb1905a12316

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.