Snipe-it: Show Recursive Asset Assignments Under User Assignments

[rpesta]

Context: We have a handful of assets assigned to our users, including "stationary" equipment (phones, monitors, etc) and non-stationary equipment (mouse, keyboard, etc). If a user changes desks, they will take their mouse and keyboard but not their monitors or deskphone, obviously.

Issue: We want to assign a phone or monitor to a desk itself. So an asset to asset assignment. Currently, that recursive asset is not visible in the users asset page.

Observed functionality: If I assign a phone to a desk and a desk to a user, under the user's assigned assets page, it only shows the desk, NOT the phone.

Desired functionality: If I assign a phone to a desk and a desk to a user, under the user's assigned assets page, it should show BOTH the desk and the phone.

[stale[bot]]

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 marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[rpesta]

Still relevant.

[stale[bot]]

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!

[stale[bot]]

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 marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[rpesta]

Yes still relevant

[stale[bot]]

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!

[stale[bot]]

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 marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[rpesta]

Still a relevant recommendation.

On Fri, Jun 7, 2019, 4:33 PM stale[bot] [e-mail] wrote:

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 marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Don't
take it personally, we just need to keep a handle on things. Thank you for
your contributions!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/6489?email_source=notifications&email_token=AD6QWLGMWKLVPBWPQ7ORPH3PZLH37A5CNFSM4GJDVSN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXHBTVQ#issuecomment-500046294,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6QWLG5T6MKCMA3ZVZHBF3PZLH37ANCNFSM4GJDVSNQ
.

[stale[bot]]

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!

[mmorais-idealsumario]

I second the request, not just for users, but also for locations and possibly all types of objects as well. If asset A is assigned to asset B, assigned to user C in location D, when listing assets in location D, all these objects should be listed.

This is in someway related to issue #7203, which I'm currently attempting to give a shot at resolving.

[valentyntu]

Hi guys, I'm going to implement the functionality requested by @rpesta. My colleagues also need it. Assets assigned to the other assets will be shown in the user's assets for admins, in "Print all assigned" and when the user views the account. It will be configurable in general settings.

[stale[bot]]

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 marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[rpesta]

Yes still relevant.

[stale[bot]]

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!

[stale[bot]]

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 marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[rpesta]

Yes, still a desired request.

[stale[bot]]

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!

[stale[bot]]

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 marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[rpesta]

Still relevant.

[stale[bot]]

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!

[valentyntu]

@rpesta my PR was finally merged a month ago, so this feature is going to be included in some future releases. I guess you can close this thread.