mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #538] [Feature]: Check if there's any Spool with not NFCTag associated of the same brand/color/type #346
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#346
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @wreuel on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/538
Originally assigned to: @maziggy on GitHub.
Problem or Use Case
I buy 10 spools from Bambu. I receive them and keep them in storage. I also add all the details (colors, etc.) to the Filament/Inventory.
Later, when I take one of those spools and insert it into the AMS, the system creates a new entry on the Filament/Inventory for that spool.
Proposed Solution
When a spool is inserted into the AMS, if the Inventory already contains an entry with the same brand, color, and material type that does not yet have a tag associated, the system should prompt the user to link the inserted spool to that existing entry instead of creating a new one.
This would prevent duplicate inventory entries and improve inventory consistency.
Alternatives Considered
No response
Feature Category
Other
Priority
Would improve my workflow
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Mar 12, 2026):
Is it for the internal inventory or Spoolman?
@wreuel commented on GitHub (Mar 12, 2026):
I did thinking about the internal inventory
@wreuel commented on GitHub (Mar 15, 2026):
Even this one that is practically ready? Has all the necessary tests and so on? That don't make sense at all @maziggy
@maziggy commented on GitHub (Mar 24, 2026):
Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!