Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User info for print job #2576

Merged
merged 2 commits into from
Apr 24, 2018

Conversation

malnvenshorn
Copy link

What does this PR do and why is it necessary?

Adding user information to the printer state so it is possible to retrieve the user who started the current print job. This is a useful information in a multi-user environment. A use case might be a print history where the admin can see who used the printer, e.g. for billing purposes.

How was it tested? How can it be tested by the reviewer?

Started print in the web interface and checked the printingUser with the job API.
Confirmed that the printingUser was set the null after the print finished/failed/was cancelled.
Also tested the same with 'print after loading'.
Haven't tested with 'print after slicing'.

Any background context you want to provide?

What are the relevant tickets if any?

#652
#1545

Screenshots (if appropriate)

Further notes

Applied changes you mentioned in #2570. Opened a new PR because I used the devel branch for my changes in the previous PR.

@foosel foosel self-assigned this Apr 24, 2018
@foosel foosel added the needs review This PR needs a review label Apr 24, 2018
@foosel foosel merged commit b41df46 into OctoPrint:maintenance Apr 24, 2018
@foosel foosel removed the needs review This PR needs a review label Apr 24, 2018
@foosel foosel removed their assignment Apr 24, 2018
@foosel foosel added this to the 1.3.9 milestone Jun 18, 2018
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants