Feature Request: Bulk Audit - Location Changing?

[innocuoussoul]

Server (please complete the following information):

• Snipe-IT Version
• OS: [e.g. Ubuntu, CentOS]
• Web Server: [e.g. Apache, IIS]
• PHP Version

Is your feature request related to a problem? Please describe.
It's annoying that we can audit a location but cant actually move those assets to those locations without checking in. Ideally, I want to be able to send one of my techs into a space and audit a location to make sure our stuff stays current.

Describe the solution you'd like
An option to confirm location change. What's the point of the audit if we can't see if the location matches and can't action on the audit.

[marrodox]

I second this, this would be incredibly useful in my deployment.

[jacobsen9026]

It in the works on the dev branch and I created a pull request with and additional option to checkout to the location if not already checked out to a user.

#7580

[innocuoussoul]

It looks like this was already implemented in the dev branch for 5.0, is this pr different?

[jacobsen9026]

I improved the logic of the change location check currently on the dev branch. It wasn't checking if the asset was already checked out before setting it's new location.

The rest of my PR is (not directly related to this issue) to add the functionality to properly check out assets that are not assigned to users already via the bulk audit page. Which has been requested before and I really could have used myself so I built it.

[innocuoussoul]

This is awesome thank you!

[stale]

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!

[jacobsen9026]

Yes

…

On Fri, Jan 10, 2020, 1:07 PM stale[bot] ***@***.***> 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 commented. Reply to this email directly, view it on GitHub <#7365?email_source=notifications&email_token=AGYN2XC2FKMFU5E5B4342ADQ5C2MHA5CNFSM4INFYM42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIUXXHY#issuecomment-573143967>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGYN2XET7PHB3DIXNY2PGETQ5C2MHANCNFSM4INFYM4Q> .

[stale]

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!

[collectingapples]

If anyone gets any manner of bulk location changing working I would be so happy. The ability to audit a location and have the stuff I scan moved into that location would be huge. I guess I don't really understand what auditing would even mean without that ability. I am currently trying to wrap my mind around what the audit feature does at all currently.

If I could also have the stuff I fail to scan be removed to another location, like some kind of "missing inventory", that would be a real dream.

[stale]

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!

[stale]

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.

[collectingapples]

Still important

…

On Sat, Apr 11, 2020, 10:17 AM stale[bot] ***@***.***> wrote: Closed #7365 <#7365>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7365 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOOYXVOLJR4Y3CF5VQU2HA3RMB3XNANCNFSM4INFYM4Q> .