Data validation for importing resources

Each table lists the CSV columns supported for a resource, the accepted values for each column, whether the column is required, and any length or range limits. The rules below apply to every resource and are not repeated in each table.

Rule	Applies to	Accepted values
File size	All imports	Up to 5,000 data rows. Empty rows and columns are removed, and values are trimmed.
Columns	All imports	Headers can be in the user’s language or in English. Unknown or duplicate columns reject the entire file. Calculated columns, such as `Remaining`, `Available`, `Age`, `Current Value`, and `EOL Date`, are ignored.
Dates	Every date column	Use `YYYY-MM-DD`, `YYYY/MM/DD`, `YYYY.MM.DD`, `MM-DD-YYYY`, `MM/DD/YYYY`, or `MM.DD.YYYY`. Purchase Date cannot be in the future.
Purchase Cost	Every cost column	Enter an amount with up to 2 decimal places, optional thousands separators, and an optional currency code, for example `1,265.89 EUR`. The accepted range is `0` to `9,999,999,999.99`. If no currency is provided, the site’s default currency is used; otherwise, `USD` is used.
Cost unit	Licenses, Accessories, Components	Add (Total), (Per item), or (Per seat) after the currency, for example `400.64 USD` (Total).
Yes/No columns	Requestable, Reassignable	Use `1`, `0`, `true`, or `false`. Empty values are treated as No.
Reference data	Any column that points to Reference Data	Use the name, case-insensitive, or numeric ID of an existing item. Missing items can be created from the preview by selecting Generate data.
Category	Any Category column	The category type must match the resource, for example a License category for licenses.
Linked Issues	Every resource with this column	Enter comma-separated Jira issue keys. Each key must exist.
Custom fields	Assets, Licenses, Accessories, Components, Consumables	Use the custom field name as the header. The value must match the field type and format. For assets, any field marked as required in the model’s fieldset must be filled.

Assets

Assets have 20 standard columns plus custom fields. In update mode, only Asset Tag is required. It must match an existing asset, and any columns omitted from the file are not changed.

No	Field	Value	Required	Length
1	Name	Any text	Yes	Max: 100 characters
2	Asset Tag	Unique string. The value must not already exist and must not be duplicated in the selected rows. If left empty, it is generated when auto-increment asset tags is enabled.	Yes	Max: 100 characters
3	Model	Asset Model name defined in Reference Data → Asset Models	Yes	NA
4	Status	Status Label name defined in Reference Data → Status Labels	Yes	NA
5	Inventory	Inventory name defined in Reference Data → Inventories	No	NA
6	Serial	Any text. A serial number already used by the same manufacturer, either in the system or in the file, shows a warning but does not block the import.	No	Max: 255 characters
7	Assigned To	Depends on Checkout Type (#14): User → one active Jira user’s display name; Asset → Asset Name (TAG); Location → location name. Requires a Status (#4) with a Deployable status type.	No	NA
8	Order Number	Any text	No	Max: 100 characters
9	Purchase Date	A date in one of the accepted formats, for example `2020-03-06`. Cannot be in the future.	No	NA
10	Purchase Cost	Number with up to 2 decimal places, followed by an optional currency code, for example `265.89 USD`. If no currency is provided, the site’s default currency is used; otherwise, USD is used.	No	Min: `0`, Max: `9999999999.99`
11	Warranty Months	Whole number	No	Min: `1`, Max: `999`
12	Department	Department name defined in Reference Data → Departments	No	NA
13	Notes	Any text	No	Max: 255 characters
14	Checkout Type	Asset, Location, or User. Default is User.	No	NA
15	Location	Location name defined in Reference Data → Locations	No	NA
16	Supplier	Supplier name defined in Reference Data → Suppliers	No	NA
17	Linked Issues	Comma-separated Jira issue keys. Each key must exist.	No	NA
18	Last Checkout	A date in one of the accepted formats. Used only when Assigned To is set. Cannot be in the future; defaults to today.	No	NA
19	Expected Checkin	A date in one of the accepted formats. Used only when Assigned To is set. Must be on or after Last Checkout.	No	NA
20	Requestable	Use `1`, `0`, `true`, or `false`. Default is `0`.	No	NA
21	Custom fields	Use the custom field name as the header. The value must match the field type. Required when the model’s fieldset marks the field as required.	Conditional	Per field

Licenses

Licenses require Name, Category, Manufacturer, and Seats. Seats must cover every assigned user and asset.

No	Field	Value	Required	Length
1	Name	Any text	Yes	Max: 100 characters
2	Category	Category name defined in Reference Data → Categories, with type License	Yes	NA
3	Manufacturer	Manufacturer name defined in Reference Data → Manufacturers	Yes	NA
4	Seats	Whole number. Must be at least the number of distinct users in Assigned To plus the number of assets in Asset Assigned.	Yes	Min: 1, Max: 10000
5	Serial	Any text	No	Max: 255 characters
6	Supplier	Supplier name defined in Reference Data → Suppliers	No	NA
7	Department	Department name defined in Reference Data → Departments	No	NA
8	Inventory	Inventory name defined in Reference Data → Inventories	No	NA
9	Depreciation	Depreciation name defined in Reference Data → Depreciations	No	NA
10	Assigned To	Active Jira users’ display names, separated by a comma and a space, for example Jane Doe, John Smith. Duplicates are removed.	No	NA
11	Asset Assigned	Assets in the format Asset Name (TAG), separated by commas. Each asset must exist. Duplicates are removed.	No	NA
12	Licensed To Name	Any text	No	Max: 255 characters
13	Licensed To Email	Email address	No	Max: 50 characters
14	Order Number	Any text	No	Max: 100 characters
15	Purchase Order	Any text	No	Max: 255 characters
16	Purchase / Renewal Date	A date in one of the accepted formats. Cannot be in the future.	No	NA
17	Purchase Cost	Amount with optional currency and optional unit, either (Per seat) or (Total), for example `120.00 USD` (Per seat).	No	Min: `0`, Max: `9999999999.99`
18	Reassignable	Use `1`, `0`, `true`, or `false`. Default is `0`.	No	NA
19	Notes	Any text	No	Max: 255 characters
20	Linked Issues	Comma-separated Jira issue keys. Each key must exist.	No	NA
21	Custom fields	Use the custom field name as the header. The value must match the field type.	No	Per field

Accessories

Accessories require Name, Category, and Quantity. Min Quantity cannot be greater than Quantity.

No	Field	Value	Required	Length
1	Name	Any text	Yes	Max: 100 characters
2	Category	Category name defined in Reference Data → Categories, with type Accessory	Yes	NA
3	Quantity	Whole number	Yes	Min: `1`, Max: `10000`
4	Min Quantity	Whole number. Must not be greater than Quantity.	No	Min: `1`, Max: `100`
5	Manufacturer	Manufacturer name defined in Reference Data → Manufacturers	No	NA
6	Supplier	Supplier name defined in Reference Data → Suppliers	No	NA
7	Department	Department name defined in Reference Data → Departments	No	NA
8	Location	Location name defined in Reference Data → Locations	No	NA
9	Inventory	Inventory name defined in Reference Data → Inventories	No	NA
10	Model Number	Any text	No	Max: 100 characters
11	Order Number	Any text	No	Max: 100 characters
12	Purchase Date	A date in one of the accepted formats. Cannot be in the future.	No	NA
13	Purchase Cost	Amount with optional currency and optional unit, either (Per item) or (Total), for example `25.50 USD` (Per item).	No	Min: `0`, Max: `9999999999.99`
14	Notes	Any text	No	Max: 255 characters
15	Linked Issues	Comma-separated Jira issue keys. Each key must exist.	No	NA
16	Custom fields	Use the custom field name as the header. The value must match the field type.	No	Per field

Components

Components require Name, Category, and Quantity. They do not include Manufacturer or Supplier columns.

No	Field	Value	Required	Length
1	Name	Any text	Yes	Max: 100 characters
2	Category	Category name defined in Reference Data → Categories, with type Component	Yes	NA
3	Quantity	Whole number	Yes	Min: `1`, Max: `10000`
4	Min Quantity	Whole number. Must not be greater than Quantity.	No	Min: `1`, Max: `100`
5	Serial	Any text	No	Max: 255 characters
6	Department	Department name defined in Reference Data → Departments	No	NA
7	Location	Location name defined in Reference Data → Locations	No	NA
8	Inventory	Inventory name defined in Reference Data → Inventories	No	NA
9	Order Number	Any text	No	Max: 100 characters
10	Purchase Date	A date in one of the accepted formats. Cannot be in the future.	No	NA
11	Purchase Cost	Amount followed by a currency and an optional unit, either (Per item) or (Total), for example `400.64 USD` (Per item). A unit requires a currency before it.	No	Min: `0`, Max: `9999999999.99`
12	Notes	Any text	No	Max: 255 characters
13	Linked Issues	Comma-separated Jira issue keys. Each key must exist.	No	NA
14	Custom fields	Use the custom field name as the header. The value must match the field type.	No	Per field

Consumables

Consumables require Name, Category, and Quantity. Purchase Cost does not support a cost unit.

No	Field	Value	Required	Length
1	Name	Any text	Yes	Max: 100 characters
2	Category	Category name defined in Reference Data → Categories, with type Consumable	Yes	NA
3	Quantity	Whole number	Yes	Min: `1`, Max: `10000`
4	Min Quantity	Whole number. Must not be greater than Quantity.	No	Min: `1`, Max: `100`
5	Manufacturer	Manufacturer name defined in Reference Data → Manufacturers	No	NA
6	Department	Department name defined in Reference Data → Departments	No	NA
7	Location	Location name defined in Reference Data → Locations	No	NA
8	Inventory	Inventory name defined in Reference Data → Inventories	No	NA
9	Model Number	Any text	No	Max: 100 characters
10	Item No	Any text	No	Max: 255 characters
11	Order Number	Any text	No	Max: 100 characters
12	Purchase Date	A date in one of the accepted formats. Cannot be in the future.	No	NA
13	Purchase Cost	Number with up to 2 decimal places, followed by an optional currency code, for example `12.99 USD`.	No	Min: `0`, Max: `9999999999.99`
14	Notes	Any text	No	Max: 255 characters
15	Linked Issues	Comma-separated Jira issue keys. Each key must exist.	No	NA
16	Custom fields	Use the custom field name as the header. The value must match the field type.	No	Per field