Fixed #18475 - reference the correct model when checking in an asset via import#18476
Merged
snipe merged 1 commit intogrokability:developfrom Jan 23, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As noted in #18475, when updating an asset that is checked out to a location via the importer and part of the update is re-assigning the asset to a different location then the action log would record the "check in" as coming from a User with the same id as the original location.
This is because we were always referencing a user by calling
User::find($asset->assigned_to). This has been changed so that we pass the model that is currently assigned to theCheckoutableCheckedInevent.Fixes #18475