Daniel Meltzer a5764351f7 Migrate weird assigned_type issues, Issue #3972 (#3973) ... For a while, prior to 987536930, we did not null assigned_type on checkin. This migration manually nulls all assigned_type fields if assigned_to is unset. Add a test to AssetTest for this as well...kind of. We need to extract an Asset::checkin() method for 4.1 that mirrors Asset::checkOut() to really test this. This also fixes a separate (but related) issue. The Asset importer did not set assigned_type when importing and creating users. In this instance, we assume that if assigned_to is set and assigned_type is not, then the item was checked out to a user and update the DB accordingly. Also add a check in ImporterTest for this issue.		2017-09-18 16:40:13 -07:00
..
AccessoryImporter.php	Importer tests + Fixes (#3733)	2017-07-11 20:37:02 -07:00
AssetImporter.php	Check for status_id key - related to #3928	2017-09-08 17:24:28 -07:00
ComponentImporter.php	Importer tests + Fixes (#3733)	2017-07-11 20:37:02 -07:00
ConsumableImporter.php	Importer tests + Fixes (#3733)	2017-07-11 20:37:02 -07:00
import_mappings.md	Importer tests + Fixes (#3733)	2017-07-11 20:37:02 -07:00
Importer.php	Custom field import repair (#3968)	2017-09-18 12:29:08 -07:00
ItemImporter.php	Migrate weird assigned_type issues, Issue #3972 (#3973)	2017-09-18 16:40:13 -07:00
LicenseImporter.php	Importer tests + Fixes (#3733)	2017-07-11 20:37:02 -07:00
UserImporter.php	Importer tests + Fixes (#3733)	2017-07-11 20:37:02 -07:00