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

Licenses assigned to assets - users not updated in license overview #10753

Closed
2 tasks done
timjaeckel opened this issue Mar 1, 2022 · 0 comments
Closed
2 tasks done
Assignees
Labels
licenses ❓ not sure if bug This issue has not been confirmed as a bug yet

Comments

@timjaeckel
Copy link

Debug mode

Describe the bug

If a license is assigned to an asset, and the asset is assigned to a person, the license overview shows the person's name under the "User" field.

If the license stays with the asset and the asset is taken back and assigned to another person, the "User" field in the license overview is not updated and the old person remains in it.

Reproduction steps

  1. Assign an asset to a person 'A'
  2. Assign a license to an asset
  3. Take the asset back from the person 'A'
  4. Assign an asset to a person 'B'
  5. Select the license and go to the "licenses" tab
  6. The assigned license shows the old user

Expected behavior

I would expect/wish that when I assign an asset to someone else, the user is automatically updated in the license overview. In our case, this sometimes leads to problems.

Screenshots

issue

Snipe-IT Version

5.4.0

Operating System

Windows Server 2019

Web Server

IIS

PHP Version

7.4.10

Operating System

Windows 10 Prof. x64

Browser

Microsoft Edge (Chromium)

Version

98

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
licenses ❓ not sure if bug This issue has not been confirmed as a bug yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants