[BUG] License check in goes to wrong target

[Diniver]

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

• [Yes] I have enabled debug mode
• [Yes] I have read checked the Common Issues page

Describe the bug
When checking in a license from user/asset, does not appear in user/asset history.

To Reproduce
Steps to reproduce the behavior:

1. Check out license to user/asset
2. Check in license
3. Open user history - you can see only check out

Expected behavior
User/asset history should display full trace for check in and check out.

Screenshots

Server (please complete the following information):

• Snipe-IT Version - v4.7.7 build 4160 (gb8f7cd81e)
• OS: Ubuntu 18.04.3 LTS
• Web Server: Apache 2.4.29
• PHP Version 7.2.19

Additional context
Reproducible in demo website.

I am fixing the problem manually by editing the action_logs sql table. Changing target_id and target_type to the appropriate values.

P.S. I am not sure if it was design that way. I believe it was not acting like that in previous patches.

Regards,
Dinvier

==EDIT==
I did some digging and enabling debug mode.
After check in the resulst are as follow:

[Diniver]

Hi all,
Do you have any update of this?

[Diniver]

I have ran an old version (4.6.10) and there everything is fine:

[Diniver]

In version 4.8.0 the problem still persist.

[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!

[Diniver]

The bug still persist.

[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!

[Diniver]

The bug still persist in version 4.9.0

[Diniver]

The bug still persist in version 4.9.1
@snipe Would you be able to have a look?

[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!

[Diniver]

The bug still persist.

[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!

[Diniver]

Issue still occurring and reproducible in demo website

Version v4.9.3 - build 4395

[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!

[Diniver]

Still reproducible in Version v4.9.4 - build 4437

@snipe is there any chance this will be fixed for 5.0?

[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!

[Diniver]

Issue solved in 5.0.1