CHANGELOG.md

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[14.0.0] - 2026-08-06

Requires NetBox >= 4.6.0. NetBox 4.5.x is not supported by this release.

Breaking Changes

• Minimum NetBox raised from 4.5.4 to 4.6.0. Migration 0006 depends on users.0016_default_ordering_indexes, which first ships in NetBox 4.6.0. On 4.5.x, migrate aborts with NodeNotFoundError before applying anything.

• The seven inventory models now inherit PrimaryModel instead of NetBoxModel. description narrows from 255 to 200 characters. No description is ever shortened for you. Migration 0007 checks every row first and, if any exceeds 200 characters, rolls back and lists the offending model, primary key and length so you can decide what to keep — move the overflow into comments, or trim it. Re-run migrate afterwards. To see the same list before upgrading:

  Asset.objects.annotate(l=Length('description')).filter(l__gt=200).values_list('pk', 'description')
  

  Repeat for AssetService, Contract, Contractor and Invoice.

Added

• Contacts on plugin objects. Asset, Asset Service, Contract, Contractor, External Inventory, Invoice and RMA now support NetBox contacts. Each gains a Contacts tab on its detail page where tenancy.Contact records can be assigned with a role and priority, plus contact, contact_role and contact_group filters in the UI and REST API, an optional Contacts table column, and contacts in GraphQL as both an output field and a filter. Contacts are stored as ContactAssignment rows, so this adds no database columns. Contacts are intentionally not exposed on the plugin's REST serializers, matching NetBox core — read and write them through /api/tenancy/contact-assignments/.

  Assignment roles are not created by the plugin. To record the ABRA responsible person, create a Owner contact role under Organization → Contact Roles.

• Ownership on plugin objects. The same seven models gain NetBox's owner field (users.Owner — a named set of NetBox users and groups, distinct from tenancy). Available on the edit form, in bulk edit (nullable), in CSV import by Owner name, as optional Owner and Owner Group table columns, as owner/owner_id/owner_group/owner_group_id filters, in the REST API, and in GraphQL as both an output field and a filter. API list endpoints select_related the owner to avoid an extra query per row.

  Migration 0006 adds a nullable owner foreign key to each of the seven tables.

• description and comments on External Inventory and RMA. Both models previously lacked these columns while their forms offered a comments box, so anything typed there was silently discarded on save. Migration 0007 adds the columns and the fields now persist.

• GraphQL filtering by owner and contacts. NetBox 4.6 exposes owner as an output field but ships no owner filter mixin, so the plugin provides inventory_monitor.graphql.filter_mixins .OwnerFilterMixin. Owner-group filtering works by nesting: owner: { group: { name: ... } }.

• Contacts prefetching on list views. BaseTable._set_prefetches stops at the GenericRelation, so enabling the Contacts column previously cost one query per contact assignment.

• inventory_monitor/tests/test_contacts.py pinning the feature registration, the Contacts URL wiring (which fails silently when broken), the contact/owner filters, and that each edit form renders exactly one owner widget.

• Note for the ABRA importer. ExternalInventory.person_id stores ABRA's personalnumber, not ABRA's person_id. The abra_contact_id custom field on tenancy.Contact is named after the latter, so joining the two matches zero rows.

Fixed

• Duplicate owner field on edit forms. templates/htmx/form.html and templates/generic/bulk_edit.html render owner/owner_group unconditionally, so listing them in a FieldSet emitted the widget twice. On submit the browser sent both values and the second overwrote the user's choice. Affected six of the seven edit forms plus three bulk-edit forms.

• docs/graphql-filters.md documented lookup names that do not exist. icontains, startswith, endswith and in are really i_contains, starts_with, ends_with and in_list, so every string-filter example in that document failed schema validation. The document now also covers the owner and contact filters, the AND/OR/NOT combinators, and which models support contacts and ownership. Every example in it is executed against the live schema.

Changed

• Filtersets, forms, tables and serializers now inherit NetBox's PrimaryModel* base classes instead of hand-assembled owner mixins, which also fixes the mixin MRO to match core's ordering.
• StrFilterLookup[str] replaced with the bare StrFilterLookup throughout the GraphQL filters; strawberry-django 0.86.4 defines it as non-generic and warns that the type argument is ignored.

[13.5.0] - 2026-08-05

Added

• Color-coded Service End and Warranty End dates. The Service End and Warranty End columns in asset tables (and Service End in asset service tables) now render each date as a badge — red when the date has passed, orange when it falls within the configured warning window, green when it is further out or open-ended. Hovering a badge shows the same human-readable message as the status bars ("Expired 11 years ago", "Expires in 45 days"). Assets with several services get one badge per service, aligned with the Service Start and Service Status columns. A period with a start but no end is open-ended coverage and shows a green ∞ badge; a record with no dates at all keeps the usual placeholder. The badges export as plain ISO dates, matching the other date columns. (#22)
• Asset type badges in the asset table now pick black or white text based on the type color, using NetBox's fgcolor filter. Dark type colors such as blue or purple were previously unreadable. (#22)
• Expired and expiring date badges carry an icon in addition to their color, so the "needs attention" states survive color blindness and greyscale printing (WCAG 1.4.1). Every badge and status bar also exposes an aria-label. (#22)
• Status bars on contract, invoice, asset and asset service detail pages now show the date range on hover, which previously only the asset list did.
• Service Status and Warranty Status filters on the Asset list, matching the color bands above: Expired / Expiring soon / Valid / No service records (Not set for warranty). Both are multi-select and return the union of the selected bands. Service Status uses any-match semantics — an asset with one expired and one valid service appears under both. Available in the UI and over REST (?service_status=expired). (#22)

Fixed

• The date badges and the status bars could disagree. The badges used a second, parallel status function, so a period that had not started yet showed blue "Starts in 30 days" in the status column but green "Valid until …" in the end-date column, and an object with no dates at all showed a placeholder in one and a green badge in the other. Both now read the same get_<type>_status() through the get_status template filter, so they cannot diverge. Verified across 244 rendered row/column pairs. (#22)
• Warranty Start (asset tables) and Service Start (asset service tables) rendered dates in the localized long format, e.g. "June 3, 2022", while every other date in the plugin uses ISO YYYY-MM-DD. Both now use NetBox's DateColumn, so all date columns and CSV exports agree. (#22)
• Date status messages said "Expired in 0 days" for a date falling on today. They now read "Expired today" / "Expires today". This also affects the existing Service, Warranty and Invoicing status bars.

Changed

• Status bars and date badges are rendered by two shared includes (inc/status_badge.html, inc/date_badge.html) instead of hand-built template strings. role="progressbar" was dropped from the bars — they are always full width, so they label a state rather than measure progress, and the role made screen readers announce a progress bar with nothing to report. All tooltips now use data-bs-toggle="tooltip" rather than a mix of Bootstrap and bare title attributes.
• warning_days now falls back to defaults (service: 60, warranty: 60, invoicing: 30) when a key is not configured, so color indicators work out of the box. Previously a missing key meant no colors at all. Deployments that relied on omitting warning_days to suppress color indicators will now see them — set the key explicitly to None (e.g. "warning_days": {"service": None}) to keep them off.

[13.4.1] - 2026-06-18

Fixed

• Added the missing currency field to the Invoice REST API serializer (InvoiceSerializer). The field existed on the model, form, table, and filterset but was absent from the API, so invoice currency could not be read or written via REST/GraphQL. (#8)

[13.4.0] - 2026-05-11

Changed

• Expanded NetBox compatibility window to 4.5.4 – 4.6.99. The plugin now installs on NetBox 4.6.x (Django 6.0) in addition to 4.5.x. No functional or API changes — verified that all NetBox APIs used by the plugin (NetBoxModel, NetBoxModelForm, NetBoxTable, NetBoxModelFilterSet, NetBoxModelSerializer, PluginTemplateExtension.models, ObjectType, RestrictedQuerySet, ChoiceSet) remain stable across both versions.
• Widened django dependency pin to >=5.0,<7.0 so the pip resolver accepts the Django 6.0 shipped with NetBox 4.6.

[13.3.0] - 2026-03-19

Breaking Changes

• Date status indicators now require explicit configuration. Warranty and Service status progress bars (on detail pages and in table columns) are no longer shown by default. You must configure warning_days in plugin settings to enable color-coded progress bars. Without configuration, status columns fall back to displaying the date range (e.g. 2025-03-19 — 2026-12-19) instead of a placeholder dash. See Configuration for details.

Added

• "Assets (Service Contract)" tab on Contract detail page: New tab displays assets linked to the contract through asset services (AssetService), complementing the existing "Assets (Order Contract)" tab which shows directly ordered assets. Includes a "Show only active services" toggle to filter out assets whose services have expired (service_end < today). Supports full table configuration and filtering via the standard Asset filterset.

• Configurable color-coded status columns: New "Service Status", "Warranty Status", and "Invoicing Status" columns with progress bar indicators (red = expired, orange = expiring within threshold, green = valid, blue = future start). Hover tooltip shows the date range. Date columns (start/end) remain as plain text. Available on Asset, Contract, and Invoice tables. Requires warning_days config — each attribute is independently configurable.

• "Service Start" column in asset tables: New column showing service start dates alongside the existing "Service End" column.

• Humanized time deltas: Status progress bars now show "3 months ago", "2 years ago" instead of raw day counts for large durations (< 90 days → days, < 2 years → months, 2+ years → years).

• Invoicing status for Contract and Invoice models: New DateStatusMixin on Contract and Invoice with get_invoicing_status() method. New "Invoicing Status" column available in Contract and Invoice tables.

Changed

• Default table columns updated: Status columns (warranty_status, services_status, invoicing_status, service_status) are now shown by default. Start/end date columns remain available via Configure Table.

• Consistent date format: All date displays in the plugin now use YYYY-MM-DD format (previously some used YYYY-M-DD without leading zero).

[13.2.0] - 2026-03-19

Added

• Asset "Has Duplicates" filter: New boolean filter on the Asset list view (UI filter form and REST API) that identifies assets with duplicate serial numbers. Useful for data hygiene — quickly find assets that were accidentally entered more than once. Supports three states: Yes (show only duplicates), No (show only unique serials), All (no filtering).

[13.1.1] - 2026-03-19

Fixed

• AssetService CSV import: Asset lookup now uses serial field instead of primary key. Previously, importing asset-services via CSV with serial numbers (e.g. ABCDE39H1AC) failed with "Object not found" because the form attempted to match the value against the numeric primary key.

[13.1.0] - 2026-03-06

Requires NetBox >= 4.5.4 (strawberry-graphql-django >= 0.79.0). NetBox 4.5.0–4.5.3 is not supported by this release.

Breaking Changes

• Minimum NetBox version raised to 4.5.4. The GraphQL layer now uses StrFilterLookup (introduced in strawberry-graphql-django 0.79.0, shipped with NetBox 4.5.4). Installations running NetBox 4.5.0–4.5.3 will fail to start. Use inventory-monitor v13.0.x for those versions.

• GraphQL filter types changed. All CharField/TextField filter fields migrated from FilterLookup[str] to StrFilterLookup[str]. This eliminates DuplicatedTypeName schema errors introduced in strawberry-graphql-django 0.79.0. Custom GraphQL clients or tooling that relied on the old FilterLookup type name in introspection results may need updating.

Added

• Optional netbox-attachments integration (re-introduced; requires netbox-attachments >= 11.0.0).
  • Enable with enable_netbox_attachments: True in plugin config (default: False).
  • Adds attachment counts to Contract and Invoice list views.
  • Plugin starts normally without netbox-attachments installed when the setting is disabled. See docs/netbox-attachments.md for setup instructions.
  • Note: versions 13.0.x had no netbox-attachments support. If you used netbox-attachments with inventory-monitor 12.x, upgrade netbox-attachments to >= 11.0.0 before enabling this setting.

Fixed

• Removed undocumented cross-column serial GraphQL filter from RMA documentation. The filter had no resolver and would raise a runtime error when queried. Use original_serial or replacement_serial filters instead.

[13.0.x]

See git history for changes in the 13.0.x series.