[GH-ISSUE #730] [Feature]: Feature Request: Per-User Print Statistics & User Assignment for Direct Prints #487

New issue

Closed

opened 2026-05-07 00:10:46 +02:00 by BreizhHardware · 20 comments

BreizhHardware commented 2026-05-07 00:10:46 +02:00

Owner

Copy link

Originally created by @3823u44238 on GitHub (Mar 17, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/730

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

First of all, I just want to say – Bambuddy is absolutely amazing. The work you've put into this project is incredible, and it's been a game-changer for managing our 3D printers at our university. Seriously, hats off to you!
We're running Bambuddy in a university FH environment with multiple students and 5 Bambu Lab printers. We have two feature requests that would make Bambuddy even more powerful for multi-user setups:

1. Per-User Print Statistics in Admin Dashboard
   As an admin, it would be very useful to see how much each user has printed – number of prints, filament used, print time and costs. This is important for cost tracking and billing students for material usage.
2. User Assignment for Direct Prints (not only Queue)
   Currently, a print job is only assigned to a user when it's started through the Queue. When a print is started directly via the "Print" button on a printer, no user is assigned. It would be great if direct prints were also tracked and assigned to the logged-in user who started them.
   These two features together would make Bambuddy a complete solution for university and makerspace environments where accountability and cost tracking are essential.
   Thank you again for the fantastic work – keep it up! 🙌

Proposed Solution

.

Alternatives Considered

No response

Feature Category

Print Archiving

Priority

Nice to have

Mockups or Examples

No response

Contribution

• I would be willing to help implement this feature

Checklist

• I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @3823u44238 on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/730 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case First of all, I just want to say – Bambuddy is absolutely amazing. The work you've put into this project is incredible, and it's been a game-changer for managing our 3D printers at our university. Seriously, hats off to you! We're running Bambuddy in a university FH environment with multiple students and 5 Bambu Lab printers. We have two feature requests that would make Bambuddy even more powerful for multi-user setups: 1. Per-User Print Statistics in Admin Dashboard As an admin, it would be very useful to see how much each user has printed – number of prints, filament used, print time and costs. This is important for cost tracking and billing students for material usage. 2. User Assignment for Direct Prints (not only Queue) Currently, a print job is only assigned to a user when it's started through the Queue. When a print is started directly via the "Print" button on a printer, no user is assigned. It would be great if direct prints were also tracked and assigned to the logged-in user who started them. These two features together would make Bambuddy a complete solution for university and makerspace environments where accountability and cost tracking are essential. Thank you again for the fantastic work – keep it up! 🙌 ### Proposed Solution . ### Alternatives Considered _No response_ ### Feature Category Print Archiving ### Priority Nice to have ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware 2026-05-07 00:10:46 +02:00

• closed this issue
• added the
  bug
  label

BreizhHardware commented 2026-05-07 00:10:47 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Mar 17, 2026):

Thank you for the flowers :)

This is something we certainly can look into. I'll add it to the "work queue".

<!-- gh-comment-id:4074404007 --> @maziggy commented on GitHub (Mar 17, 2026): Thank you for the flowers :) This is something we certainly can look into. I'll add it to the "work queue".

BreizhHardware commented 2026-05-07 00:10:47 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Mar 24, 2026):

Before we commit to building this, I'd like to gauge community interest. If you'd find this feature useful, please give this issue a thumbs up (👍) reaction so we can prioritize accordingly.

<!-- gh-comment-id:4116109388 --> @maziggy commented on GitHub (Mar 24, 2026): Before we commit to building this, I'd like to gauge community interest. If you'd find this feature useful, please give this issue a thumbs up (👍) reaction so we can prioritize accordingly.

BreizhHardware commented 2026-05-07 00:10:47 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Mar 28, 2026):

Per-User Print Statistics in Admin Dashboard

Can you please explain more detailed? Should it be an admin only dashboard or for all users?

<!-- gh-comment-id:4147883373 --> @maziggy commented on GitHub (Mar 28, 2026): >Per-User Print Statistics in Admin Dashboard Can you please explain more detailed? Should it be an admin only dashboard or for all users?

BreizhHardware commented 2026-05-07 00:10:47 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Mar 30, 2026):

---

To answer your question: we would love to see this as an admin feature, not necessarily for each user individually. The most useful implementation for us would be a simple dropdown in the existing Statistics page where you can select either "All Users" (current behaviour) or a specific user – and the statistics update accordingly.

The per-user view is less important for us. What matters most is that admins can filter and see usage per person.

But I want to highlight something I think is even more critical: knowing who started each print. Right now, if a print is started directly via the "Print" button on a printer card (not through the Queue), no user is assigned to it. This means the statistics and archive are incomplete. Every print should show who initiated it, regardless of how it was started.

This is not just relevant for us – I think any organization, company, or makerspace using Bambuddy in a multi-user setup would benefit enormously from this. It's the foundation for any kind of accountability or cost tracking.

The combination of: (1) user attribution on every print and (2) a per-user filter in the statistics dashboard would make Bambuddy a truly complete solution for professional and institutional environments.

Thank you again for your incredible work on this project!****

<!-- gh-comment-id:4152785819 --> @3823u44238 commented on GitHub (Mar 30, 2026): --- To answer your question: we would love to see this as an admin feature, not necessarily for each user individually. The most useful implementation for us would be a simple dropdown in the existing Statistics page where you can select either "All Users" (current behaviour) or a specific user – and the statistics update accordingly. The per-user view is less important for us. What matters most is that admins can filter and see usage per person. But I want to highlight something I think is even more critical: **knowing who started each print**. Right now, if a print is started directly via the "Print" button on a printer card (not through the Queue), no user is assigned to it. This means the statistics and archive are incomplete. Every print should show who initiated it, regardless of how it was started. This is not just relevant for us – I think any organization, company, or makerspace using Bambuddy in a multi-user setup would benefit enormously from this. It's the foundation for any kind of accountability or cost tracking. The combination of: (1) user attribution on every print and (2) a per-user filter in the statistics dashboard would make Bambuddy a truly complete solution for professional and institutional environments. Thank you again for your incredible work on this project!****

BreizhHardware commented 2026-05-07 00:10:47 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Mar 30, 2026):

Please keep in mind, that no user can be assigned if the print is started from the slicer. It only works for prints that were initiated via Bambuddy.

<!-- gh-comment-id:4152971012 --> @maziggy commented on GitHub (Mar 30, 2026): Please keep in mind, that no user can be assigned if the print is started from the slicer. It only works for prints that were initiated via Bambuddy.

BreizhHardware commented 2026-05-07 00:10:47 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Mar 30, 2026):

yes we prefer and do it this way. Not directly via slicer

<!-- gh-comment-id:4153076900 --> @3823u44238 commented on GitHub (Mar 30, 2026): yes we prefer and do it this way. Not directly via slicer

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Mar 31, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.

Docs -> https://wiki.bambuddy.cool/features/statistics/?h=per+user#per-user-filtering

---

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

<!-- gh-comment-id:4161485186 --> @maziggy commented on GitHub (Mar 31, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you. Docs -> https://wiki.bambuddy.cool/features/statistics/?h=per+user#per-user-filtering ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Apr 14, 2026):

Hi again! Thank you for implementing the per-user statistics filtering – it's already working great in the daily build!
I wanted to follow up on the second part of the request: user assignment for direct prints (not via Queue).
You mentioned that no user can be assigned if the print is started from the slicer, which makes total sense. But what about prints started via the "Print" button directly on the printer card in Bambuddy (not from the slicer, not from the Queue)?
When a user clicks that button, Bambuddy receives an authenticated API request with a JWT token – so the logged-in user is technically known at that moment. Wouldn't it be possible to read the user from the JWT token and assign it as created_by_id on the resulting archive?
From a user perspective, the difference between "Print via Queue" and "Print directly" is just one extra click – but the tracking outcome is completely different. Both actions are performed inside Bambuddy by an authenticated user, so it feels like the user should be assignable in both cases.
Would love to hear your thoughts on whether this is technically feasible!

<!-- gh-comment-id:4242588786 --> @3823u44238 commented on GitHub (Apr 14, 2026): Hi again! Thank you for implementing the per-user statistics filtering – it's already working great in the daily build! I wanted to follow up on the second part of the request: user assignment for direct prints (not via Queue). You mentioned that no user can be assigned if the print is started from the slicer, which makes total sense. But what about prints started via the "Print" button directly on the printer card in Bambuddy (not from the slicer, not from the Queue)? When a user clicks that button, Bambuddy receives an authenticated API request with a JWT token – so the logged-in user is technically known at that moment. Wouldn't it be possible to read the user from the JWT token and assign it as created_by_id on the resulting archive? From a user perspective, the difference between "Print via Queue" and "Print directly" is just one extra click – but the tracking outcome is completely different. Both actions are performed inside Bambuddy by an authenticated user, so it feels like the user should be assignable in both cases. Would love to hear your thoughts on whether this is technically feasible!

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Apr 14, 2026):

Available/Fixed in branch dev and available with the next release or daily build.

Hi again! Thank you for implementing the per-user statistics filtering – it's already working great in the daily build! I wanted to follow up on the second part of the request: user assignment for direct prints (not via Queue). You mentioned that no user can be assigned if the print is started from the slicer, which makes total sense. But what about prints started via the "Print" button directly on the printer card in Bambuddy (not from the slicer, not from the Queue)? When a user clicks that button, Bambuddy receives an authenticated API request with a JWT token – so the logged-in user is technically known at that moment. Wouldn't it be possible to read the user from the JWT token and assign it as created_by_id on the resulting archive? From a user perspective, the difference between "Print via Queue" and "Print directly" is just one extra click – but the tracking outcome is completely different. Both actions are performed inside Bambuddy by an authenticated user, so it feels like the user should be assignable in both cases. Would love to hear your thoughts on whether this is technically feasible!

<!-- gh-comment-id:4242727178 --> @maziggy commented on GitHub (Apr 14, 2026): Available/Fixed in branch dev and available with the next release or daily build. > Hi again! Thank you for implementing the per-user statistics filtering – it's already working great in the daily build! I wanted to follow up on the second part of the request: user assignment for direct prints (not via Queue). You mentioned that no user can be assigned if the print is started from the slicer, which makes total sense. But what about prints started via the "Print" button directly on the printer card in Bambuddy (not from the slicer, not from the Queue)? When a user clicks that button, Bambuddy receives an authenticated API request with a JWT token – so the logged-in user is technically known at that moment. Wouldn't it be possible to read the user from the JWT token and assign it as created_by_id on the resulting archive? From a user perspective, the difference between "Print via Queue" and "Print directly" is just one extra click – but the tracking outcome is completely different. Both actions are performed inside Bambuddy by an authenticated user, so it feels like the user should be assignable in both cases. Would love to hear your thoughts on whether this is technically feasible!

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Apr 21, 2026):

---

Hi! I'm Sorry somehow I cant seem to find the fix. Maybe I'm doing something wrong?
I tested all print paths with v0.2.3.1 and here are the results for user attribution (created_by_id):

• Queue: user is correctly assigned
• Direct Print button on printer card: user is NOT assigned (created_by_id = NULL)
• Print from File Manager/Library: user is NOT assigned (created_by_id = NULL)
• Reprint from Archive: user is NOT assigned (created_by_id = NULL)

It seems the fix for "Library Prints Not Attributed to User" mentioned in the 0.2.3 release notes did not take effect, or it only covers a specific code path.

Additionally, I noticed two side effects when printing via the Direct Print button on the printer card:

1. If the file does not already exist in the File Manager, Bambuddy automatically uploads it there. This is undesirable — files should only land in the Archive, not in the File Manager, unless the user explicitly uploads them.

2. This happens even when the "Create archive entry when printing from File Manager" setting is set to never.

All three non-queue print paths are triggered by authenticated Bambuddy users with valid JWT tokens, so the logged-in user is technically known at the time of the request. Could user attribution be extended to cover all these paths?

<!-- gh-comment-id:4287793716 --> @3823u44238 commented on GitHub (Apr 21, 2026): --- Hi! I'm Sorry somehow I cant seem to find the fix. Maybe I'm doing something wrong? I tested all print paths with `v0.2.3.1` and here are the results for user attribution (`created_by_id`): - Queue: user is correctly assigned - Direct Print button on printer card: user is NOT assigned (created_by_id = NULL) - Print from File Manager/Library: user is NOT assigned (created_by_id = NULL) - Reprint from Archive: user is NOT assigned (created_by_id = NULL) It seems the fix for "Library Prints Not Attributed to User" mentioned in the 0.2.3 release notes did not take effect, or it only covers a specific code path. Additionally, I noticed two side effects when printing via the Direct Print button on the printer card: 1. If the file does not already exist in the File Manager, Bambuddy automatically uploads it there. This is undesirable — files should only land in the Archive, not in the File Manager, unless the user explicitly uploads them. 2. This happens even when the "Create archive entry when printing from File Manager" setting is set to never. All three non-queue print paths are triggered by authenticated Bambuddy users with valid JWT tokens, so the logged-in user is technically known at the time of the request. Could user attribution be extended to cover all these paths?

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Apr 21, 2026):

I think something went wrong when merging new features for the release. Let me check....

<!-- gh-comment-id:4288191645 --> @maziggy commented on GitHub (Apr 21, 2026): I think something went wrong when merging new features for the release. Let me check....

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Apr 21, 2026):

I'm sorry, I forgot to merge the fixes for this issue. Hopfully all are fixed now.

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now.

---

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

<!-- gh-comment-id:4288402862 --> @maziggy commented on GitHub (Apr 21, 2026): I'm sorry, I forgot to merge the fixes for this issue. Hopfully all are fixed now. Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Apr 21, 2026):

Thank you very much!

<!-- gh-comment-id:4288864877 --> @3823u44238 commented on GitHub (Apr 21, 2026): Thank you very much!

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Apr 21, 2026):

Does that mean that it is working now for you?

<!-- gh-comment-id:4288980986 --> @maziggy commented on GitHub (Apr 21, 2026): Does that mean that it is working now for you?

BreizhHardware commented 2026-05-07 00:10:48 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Apr 21, 2026):

I'm waiting for the next daily build cycle to trigger so I can pull the latest image and test. I'll update you as soon as I've verified the fix in my environment tomorrow. Thanks again for the quick turnaround!

<!-- gh-comment-id:4289311068 --> @3823u44238 commented on GitHub (Apr 21, 2026): I'm waiting for the next daily build cycle to trigger so I can pull the latest image and test. I'll update you as soon as I've verified the fix in my environment tomorrow. Thanks again for the quick turnaround!

BreizhHardware commented 2026-05-07 00:10:49 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Apr 22, 2026):

Hi! After updating to v0.2.4b1 (daily build), the per-user statistics dropdown that was available in v0.2.3.1 seems to be missing from the Statistics page. Was this intentionally removed or was this a mistake?

<!-- gh-comment-id:4296696488 --> @3823u44238 commented on GitHub (Apr 22, 2026): Hi! After updating to v0.2.4b1 (daily build), the per-user statistics dropdown that was available in v0.2.3.1 seems to be missing from the Statistics page. Was this intentionally removed or was this a mistake?

BreizhHardware commented 2026-05-07 00:10:49 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Apr 22, 2026):

Nope, still there. Cache problem?

<!-- gh-comment-id:4296748831 --> @maziggy commented on GitHub (Apr 22, 2026): Nope, still there. Cache problem?

BreizhHardware commented 2026-05-07 00:10:49 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Apr 22, 2026):

oh yes it was. Thank you. I will try the different print paths. Thanks alot!

<!-- gh-comment-id:4296763510 --> @3823u44238 commented on GitHub (Apr 22, 2026): oh yes it was. Thank you. I will try the different print paths. Thanks alot!

BreizhHardware commented 2026-05-07 00:10:49 +02:00

Author

Owner

Copy link

@3823u44238 commented on GitHub (Apr 23, 2026):

Hi! Quick update after testing v0.2.4b1:

Direct Print button on printer card: user is now correctly assigned ✅
Print from File Manager: user is now correctly assigned ✅
Reprint from Archive: user is still not assigned (created_by_id = NULL) ❌

<!-- gh-comment-id:4303473037 --> @3823u44238 commented on GitHub (Apr 23, 2026): Hi! Quick update after testing v0.2.4b1: Direct Print button on printer card: user is now correctly assigned ✅ Print from File Manager: user is now correctly assigned ✅ Reprint from Archive: user is still not assigned (created_by_id = NULL) ❌

BreizhHardware commented 2026-05-07 00:10:49 +02:00

Author

Owner

Copy link

@maziggy commented on GitHub (Apr 23, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let me know it it works now.

---

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

<!-- gh-comment-id:4304322765 --> @maziggy commented on GitHub (Apr 23, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know it it works now. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

github-repo-stats

bug-report-assets

dev

0.2.4b3

0.2.4b2

0.2.4b1

pr/1114

0.2.3.2

0.2.3.1

0.2.3

0.2.3b3

0.2.3b2

0.2.3b1

0.2.2.2

0.2.2.1

0.2.2b3

0.2.2

0.2.2b2

0.2.2b1

0.2.1.1

0.2.1

0.2.1b3

0.2.1b2

0.2.1b

0.2.0

0.2.0b

0.1.5-2-ctrl

v0.2.4b4-daily.20260508

v0.2.4b2

v0.2.4b3

v0.2.4b1

v0.2.3.2

v0.2.3.1

v0.2.3

v0.2.3b3

v0.2.3b2

v0.2.3b1-daily.20260407

v0.2.3b1

v0.2.2.2

v0.2.2.1

v0.2.3b1-daily.20260318

v0.2.3b1-daily.20260317

v0.2.3b1-daily.20260316

v0.2.2

v0.2.2b4-daily.20260314

v0.2.2b4-daily.20260313

v0.2.2b3-daily.20260312

v0.2.2b3-1

v0.2.2b2

v0.2.2-b2

v0.2.2b3

v0.2.2-b1

v0.2.2b1

v0.2.1.1

v0.2.1

v0.2.1b3

v0.2.1b2

v0.2.1b

v0.2.0

v0.1.9

v0.1.8.1

v0.1.8

v0.1.7

v0.1.6.2

v0.1.6.1

v0.1.6-hotfix

v0.1.6

v0.1.6b11

v0.1.6b10

v0.1.6b9

v0.1.6b8

v0.1.6b7

v0.1.6b6

v0.1.6b5

v0.1.6b4

v0.1.6b3

v0.1.6b2

v0.1.6b

v0.1.5-final

v0.1.5b7

v0.1.5b6

v0.1.5b5

v0.1.5b4

v0.1.5b3

v0.1.5b2

v0.1.5b

v0.1.4

v0.1.3

v0.1.2-bugfix

v0.1.2-final

v0.1.2

0.1.1

Labels

Clear labels   

A1

  

automated

  

automated

  

bug

  

bug

  

Closed due to inactivity

  

contrib

  

dependencies

  

dependencies

  

duplicate

  

enhancement

  

feedback

  

hold

  

invalid

  

Notes

  

P1S

  

pull-request

Mirrored from GitHub Pull Request

  

security

  

ThumbsUp

  

user-report

  

wontfix

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

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/bambuddy-maziggy-1#487

No description provided.