Bone Collection popup cannot have shortcuts assigned #40
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/blender-bug-reports#40
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Original bug report: https://projects.blender.org/blender/blender/issues/157214
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 595.79 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: (newest version of Blender that worked as expected)
Short description of error
When trying to assign a shortcut to a bone collection operator, the shortcut isn't assigned.
Exact steps for others to reproduce the error
Add→ArmatureBonesSelect BonesAssign Shortcut...This is also the case for seemingly all other buttons in the
Bone CollectionpopupReport is clear
LLM Reasoning
Got it, let's see. The bug report has a clear title, short description, and exact steps to reproduce. The steps are numbered and detailed enough that someone can follow them. The issue is about not being able to assign shortcuts to bone collection operators, which is clearly stated. So the clarity of the text and steps is good. So the answer should be Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 5.94523
}
Report is specific
LLM Reasoning
Got it, let's analyze this bug report. The title is "Bone Collection popup cannot have shortcuts assigned". The body describes exact steps to reproduce: opening Blender, adding an armature, going through specific menus (Add → Armature, properties panel, Bone Collections), right-clicking on entries, assigning a shortcut, and checking that it doesn't work. It's about a specific feature (Bone Collection popup) and the exact steps are provided. So this is a specific issue because it's not vague; it's about a particular part of Blender (Bone Collection popup shortcuts) with detailed reproduction steps. Wait, but let me check the definition again. Specific bug reports are about a specific issue, like crashing while using a specific feature. Here, the issue is that shortcuts can't be assigned to Bone Collection popup buttons, which is a specific feature. The steps are exact, so it's specific. So the answer should be 'Specific'.
JSON Data
{
"llm_judgement": true,
"processing_time": 11.423312
}
Report flagged as NOT a duplicate by LLM
Assigning bones to collections doesnt work on the panel
https://projects.blender.org/blender/blender/issues/114652
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 545.84
Blender Version
Broken: version: 4.0.0 Beta, branch: blender-v4.0-release, commit date: 2023-11-08 20:31, hash:
aaf69376314fWorked: (newest version of Blender that worked as expected)
Short description of error
Moving one of the bones to the new collection by selecting it and pressing the assign button doesnt work on todays buil.d
Exact steps for others to reproduce the error
Create a bone, add a new collection, duplicate the bone, try moving one of the bones to the new collection by selecting it and pressing the assign button
with the m shortcut it works, just not with assign from the panel
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.
Bug Report 1 is about assigning shortcuts to Bone Collection operators—when you try to set a shortcut, it doesn't work. The steps involve right-clicking on "Select Bones" in the Bone Collections panel and trying to assign a shortcut, but it fails.
Bug Report 2 is about moving bones to collections using the assign button in the panel—selecting a bone and pressing the assign button doesn't work (though m shortcut works). So this is about assigning bones to collections via the UI button, not shortcuts.
The key difference: Report 1 is about shortcut assignment for Bone Collection operators, Report 2 is about assigning bones to collections using the panel's assign button. Different issues—one is shortcut functionality, the other is bone-to-collection assignment. So they're not the same.
JSON Data
{
"llm_judgement": false,
"processing_time": 13.22617,
"duplicate_report_number": "114652"
}
Report flagged as NOT a duplicate by LLM
Assign Automatic From Bones doesn't work in 5.0
https://projects.blender.org/blender/blender/issues/150081
System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 560.94 Opengl Backend
Blender Version
Broken: version: 5.0.0 Release Candidate, branch: blender-v5.0-release, commit date: 2025-11-12 16:43, hash:
cab24d57857cWorked: 4.5.3
Short description of error
The operator Assign Automatic From Bones doesn't work reliable. It always creates the vertex groups, but sometimes just doesn't generate any weights. I guess this might be related to the new selection state of pose bones.
I ran into this on two different rigs and it only happens in Blender 5.0.
Exact steps for others to reproduce the error
I attached a file that allows to reproduce the error. Simply open the file and execute the operator from the Weights menu. You will note that the vertex groups are created, but empty. I tried to reproduce this with the default cube and a simple bone chain, but it worked in that simple test case...
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1 is about not being able to assign shortcuts to Bone Collection operators (like "Select Bones"). The steps involve opening a new Blender instance, adding an armature, going to Bone Collections, right-clicking options, assigning a shortcut, but it doesn't work.
Bug report 2 is about the "Assign Automatic From Bones" operator in 5.0 not working reliably—sometimes creates vertex groups but no weights. The steps involve opening a specific file and executing the operator from the Weights menu, which results in empty vertex groups.
The issues are completely different: one is about shortcut assignment for Bone Collections, the other is about an operator (Assign Automatic From Bones) failing to generate weights. So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 13.106903,
"duplicate_report_number": "150081"
}
Report flagged as NOT a duplicate by LLM
Broken shortcut "Move to bone collection" (M)
https://projects.blender.org/blender/blender/issues/154878
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 NVIDIA Corporation NVIDIA 560.94 Vulkan Backend
Blender Version
Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash:
a3db93c5b259Worked: (newest version of Blender that worked as expected)
Short description of error
Error when i move a bone
Exact steps for others to reproduce the error
When i try to move a bone to another bone collection with the shortcut "m" appears this error
"Python: TypeError: BLM_OT_bonelayers.init() takes 1 positional argument but 2 were given"
I don't use to make bug reports, sorry if a made a mistake. And thanks for all your work.
LLM Reasoning
Got it, let's analyze the two bug reports. First, look at the descriptions and steps.
Bug report 1 is about not being able to assign shortcuts to bone collection operators (like "Select Bones" in the Bone Collections popup). The steps involve trying to assign a shortcut and it not working.
Bug report 2 is about a specific shortcut ("M") for moving a bone to another collection causing a Python TypeError. The error message is different, and the issue here is an error when using the shortcut, not the inability to assign shortcuts.
So the core issues are different: one is about assigning shortcuts (they don't stick), the other is about a specific shortcut causing an error during use. Therefore, they aren't the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 11.477191999999999,
"duplicate_report_number": "154878"
}
Report flagged as NOT a duplicate by LLM
Assigning a shortcut in edit mode does not work
https://projects.blender.org/blender/blender/issues/109233
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.17
Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash:
e1ccd9d4a1d3Worked: (newest version of Blender that worked as expected)
Short description of error
[Please fill out a short description of the error here]
I've written a short script to move the origin to the location where I have something selected in EDIT mode.
When I try to assign a shortcut to this by right clicking the operator it will not work in EDIT mode. You can only set a shortcut this way while in OBJECT mode.
However in the Blender Preferences I can go to Keymap and manually add the shortcut this way and it will work perfectly fine.
See video
Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1 is about Bone Collection popup not allowing shortcuts to be assigned—steps involve opening bone collections, right-clicking "Select Bones", assigning shortcut, but it doesn't work. The issue is specific to bone collection operators in that popup.
Bug report 2 is about assigning a shortcut in edit mode (for a script) not working—you can only set it in object mode, and manual keymap works. The steps are installing a script, trying to assign shortcut in edit mode, which fails.
The first is about bone collection shortcuts in a specific UI popup, the second is about a script's shortcut assignment failing in edit mode (but working in object mode). These are different contexts: one is a built-in feature (bone collections), the other is a custom script. The steps and error descriptions don't match. So they're not the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 14.102158,
"duplicate_report_number": "109233"
}
Report flagged as NOT a duplicate by LLM
Bone Collections "Select" button doesn't work in Pose Mode (Blender 5 beta)
https://projects.blender.org/blender/blender/issues/148129
System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.29 Opengl Backend
Blender Version
Broken: version: 5.0.0 Beta, branch: blender-v5.0-release, commit date: 2025-10-13 23:29, hash:
63d65bebf048Worked: The commit before 5.0 a09d0cfd8ccecb57248c6ed96ba25900eab82e0f
Short description of error
Bone Collections "Select" button doesn't seem to work in Pose Mode.
Exact steps for others to reproduce the error
Create an armature, go to pose mode, deselect the default bone, then press the Select button under Data > Bone Collections.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1 is about not being able to assign shortcuts to Bone Collection operators (like "Select Bones"). The steps involve trying to assign a shortcut and it not working.
Bug report 2 is about the "Select" button in Bone Collections not working in Pose Mode—so when you press it, nothing happens. The steps are creating an armature, going to pose mode, deselecting the bone, then pressing Select.
The issues are different: one is about shortcut assignment failing, the other is about the button itself not functioning (even without shortcuts). So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 11.519166,
"duplicate_report_number": "148129"
}