Skip to content

Asset Missing Information

Ed Mozley edited this page Nov 20, 2026 · 1 revision

πŸ“‹ Missing information - what each asset type should have, and which assets still lack it

GitHub #404, asked for by @Dr4inder - a follow-up to #200, where completeness checks were agreed as "flag, never refuse" Β· 5.8.0 Β· Internals: Missing information - Developer Guide

An asset can be recorded with what you know on day one - a notebook's name, type and serial - and the purchase details added when the invoice arrives. Until now nothing reminded anyone. Now each asset type can say which fields its assets should eventually have, and Missing information lists every asset still lacking one, naming the field.

Nothing is ever refused. The asset page, imports, the REST API and the inventory agent save exactly as they did. An expected field is a to-do, not a rule.

At a glance

Where Who
Choose what a type expects Assets β†’ Settings β†’ Asset types β†’ a type β†’ Expected information Anyone who can edit asset types
Work through the list Assets β†’ Missing information (appears once a type expects something) Anyone with access to Assets
Mark a field Not applicable The list, or the line on the asset's Key info Write access to Assets
Undo Not applicable The asset's Key info β†’ Undo Write access to Assets

Run Database Verification after upgrading.

Choosing the fields

Open an asset type and tick the fields under Expected information:

Section Fields
Identity Asset tag, Serial number, Location
Make and model Manufacturer, Model
Financial Purchase date, Purchase cost, Supplier, Cost centre, Order number, Warranty expiry
Custom fields any field in the field sets attached to this type

They are the real fields - there is no second "purchase date" to fill in. A custom field only appears when its field set is attached to the type (Settings β†’ Custom fields).

Hiding a section in the type's layout hides it from view; it does not make its fields Not applicable. A type can hide Hardware and still expect a model.

The list

Assets β†’ Missing information shows each asset still lacking something its type expects, with every missing field as a chip:

  • Filter by asset type, section (Financial, say) or a single field.
  • Click an asset to open it and fill the field in.
  • Fill a field in - from anywhere - and it leaves the list at once. There is nothing to close: the page, an import, the API and the agent all count. Clear the field and it comes back. Change what a type expects and the list follows.

The list covers the company you are working in (or every company you can see, under All companies), like every other asset list. Retired assets are not listed.

What counts as missing

Missing Filled in
No value at all Any value - including a cost of 0
Blank text, or only spaces A "No" in a yes/no field
Nothing selected (no supplier, no location)

The check is whether there is a value, not whether it is right.

Not applicable

Some fields will never be filled in for one asset - a donated laptop has no purchase cost. Not applicable puts that field aside for that asset:

  • It writes nothing into the field - no placeholder, no fake date.
  • It is recorded in the asset's history ("Not applicable: Purchase cost").
  • The asset's Key info shows it, with Undo. Undo brings the finding back if the field is still empty.

On the asset

When an asset's type expects something it lacks, Key info says so above the details: Still to fill in: Purchase date (Not applicable), Supplier (Not applicable) - and below it anything marked Not applicable: Warranty expiry (Undo). Saving a field updates the line straight away. An asset with nothing missing shows no line.

Not part of this

Deadlines, reminders, tasks raised automatically and approval steps were deliberately left out (the issue asked for none of them). Missing information is separate from Asset review, which is about two records that might be the same machine.

Related: Assets Β· Asset type profiles - design Β· Custom asset fields

FreeITSM

Getting Started

Modules

Multi-tenancy (planned)

Responses to feedback

Blue sky thinking

Bugs resolved

Pull requests

Links

Clone this wiki locally