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

Assets checked out to other assets don't change their location when the other asset is checked in or out #8097

Open
2 tasks done
eitler-terra opened this issue May 29, 2020 · 13 comments

Comments

@eitler-terra
Copy link

eitler-terra commented May 29, 2020

Please confirm you have done the following before posting your bug report:

Describe the bug
Assets checked out to other assets don't change their location when the other asset is checked in or out to other locations

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'the Asset you want to check out to another assett and check the asset out to the target asset'
  2. Go to 'the Asset witch has now an asset checked out to it and check this asset out to a location'
  3. Search for 'both assets and note that the asset witch was checked out to the asset still has the old location from the initial checkout to the other asset'

--> I reproduced this also on the online demo

Expected behavior
Expected behavior would be, that the asset witch is checked out to the other asset does change it's location according to the asset witch it is checked out to

Screenshots

image

image

image

Server (please complete the following information):

  • Snipe-IT Version: 4.9.2
  • OS: Ubuntu
  • Web Server: Apache
  • PHP Version: 7.4.4

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Chrome
  • Version: 83.0.4103.61

Error Messages

  • no Error Messages

Additional context

  • Is this a fresh install or an upgrade? : fresh install
  • What method you used to install Snipe-IT: docker
  • Indicate whether or not you've manually edited any data directly in the database: never
@eitler-terra
Copy link
Author

eitler-terra commented May 29, 2020

when I run the Asset Location Sync Comand php artisan snipeit:sync-asset-locations --output=all it seems to update the locations to the correct location, but I would need to run the comand over and over?

Thank you in advance, for your help!

@Jaspotn0612
Copy link

Adding in my support for this issue to be looked at, I have an HPE BladeSystem that has child Blades in it so we have checked the Blades out to the chassis BladeSystem. We moved a BladeSystem to another location and updated that and now we have to modify each individual Blade by checking it in and then back out again to the BladeSystem. Since these are data centre assets, it's not logical to check them out to a person as no one single person is responsible for them.

@gmintoco
Copy link

gmintoco commented Jun 2, 2020

Hi there is an existing issue for this with a bit of a workaround #7938

@stale
Copy link

stale bot commented Aug 1, 2020

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 stale bot added the stale label Aug 1, 2020
@Jaspotn0612
Copy link

yes

@stale
Copy link

stale bot commented Aug 2, 2020

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 stale bot removed the stale label Aug 2, 2020
@stale
Copy link

stale bot commented Oct 4, 2020

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 stale bot added the stale label Oct 4, 2020
@Jaspotn0612
Copy link

Yes still relevant.

@stale
Copy link

stale bot commented Oct 5, 2020

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 stale bot removed the stale label Oct 5, 2020
@justinotherguy
Copy link

still relevant :)

@stale
Copy link

stale bot commented Dec 25, 2020

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 stale bot added the stale label Dec 25, 2020
@justinotherguy
Copy link

Hello stale bot,
yes, this is still relevant. Thanks for asking :)

@stale
Copy link

stale bot commented Dec 25, 2020

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 stale bot removed the stale label Dec 25, 2020
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

4 participants