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

Unexpected Random Asset Assignment in Unaccepted Asset Screen (v7.1.16) #16161

Open
c1thunder opened this issue Feb 3, 2025 · 0 comments
Open

Comments

@c1thunder
Copy link

Unexpected Random Asset Assignment in Unaccepted Asset Screen (v7.1.16)

Description

After updating to Snipe-IT v7.1.16, I noticed an issue where the Unaccepted Asset screen displays a random asset assigned to a random user. However, checking the asset history shows no record of that user being involved.

For example, for asset SEC-PC03, the system shows that Lum Kah Yung collected the asset, but when reviewing the asset’s history, there is no mention of this user.

Image

Image

Steps to Reproduce

  1. Update Snipe-IT to v7.1.16.
  2. Navigate to the Unaccepted Assets screen.
  3. Observe that some assets display incorrect user assignments.
  4. Check the asset’s history – the user mentioned in the Unaccepted Assets screen does not appear in the logs.

Expected Behavior

  • The Unaccepted Assets screen should only display valid assignments.
  • The user shown in the Unaccepted Assets screen should match the asset’s history.

Actual Behavior

  • A random user appears in the Unaccepted Assets screen.
  • The asset history does not include any record of that user interacting with the asset.

Environment

  • Snipe-IT Version: 7.1.16
  • Operating System: WinSer 2019
  • Web Server: IIS
  • PHP Version: 8.2.26
  • Database Version: mysql
  • Browser: Edge

Additional Information

  • Issue only started after upgrading to 7.1.16.
  • No changes were made to asset assignments manually.
  • Please let me know if you need logs or additional debugging information.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant