-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Linked Asset history trail #7086
Comments
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Still relevant |
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it. |
Server (please complete the following information):
Is your feature request related to a problem? Please describe.
I would like to be able to link a specific asset/accessory/component/consumable to an asset and maintain an audit trail of which specific item was linked to the asset.
I understand that you cannot achieve this with accessories as they are assigned to people.
Both components and consumables are quantities of items and are not specific.
I have therefore utilised linking assets. However, if I deploy asset B to asset A, I can see when from the history of asset B that it was checked out to Asset A (and checked in again), however, I cannot see any mention of this link in the history of Asset A.
Describe the solution you'd like
If Asset B is checked out to Asset A, I would like the history of both Asset A and B to register this.
Describe alternatives you've considered
I tried to achieve an audit trail of 2 linked items using any of asset/accessory/component/consumable.
The text was updated successfully, but these errors were encountered: