You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Steps to Reproduce
Update Snipe-IT to v7.1.16.
Navigate to the Unaccepted Assets screen.
Observe that some assets display incorrect user assignments.
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.
The text was updated successfully, but these errors were encountered:
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.
Steps to Reproduce
Expected Behavior
Actual Behavior
Environment
Additional Information
The text was updated successfully, but these errors were encountered: