Inventory Item names should be optional #8619

Closed
opened 2025-12-29 20:38:58 +01:00 by adam · 2 comments
Owner

Originally created by @pv2b on GitHub (Sep 15, 2023).

NetBox version

v3.6.1

Feature type

Change to existing functionality

Proposed functionality

Currently, Inventory Item Names are mandatory and must be unique within the context of a single device.

I propose making Inventory Item Names optional, similar to how you can have unnamed devices.

Use case

When using the Inventory Item feature to assign an SFP to an Interface, for example, it doesn't really make any sense to have to give that SFP a name. It's role is an SFP, and it's assigned to a specific device and a specific interface. A name is unneccessary, and just creates busywork for the administrator to give it a name such as SFP19.

Database changes

Probably no database changes, I would hope that any database references to inventory items are by ID, and not by name, but I've not checked myself.

External dependencies

None.

Originally created by @pv2b on GitHub (Sep 15, 2023). ### NetBox version v3.6.1 ### Feature type Change to existing functionality ### Proposed functionality Currently, Inventory Item Names are mandatory and must be unique within the context of a single device. I propose making Inventory Item Names optional, similar to how you can have unnamed devices. ### Use case When using the Inventory Item feature to assign an SFP to an Interface, for example, it doesn't really make any sense to have to give that SFP a name. It's role is an SFP, and it's assigned to a specific device and a specific interface. A name is unneccessary, and just creates busywork for the administrator to give it a name such as SFP19. ### Database changes Probably no database changes, I would hope that any database references to inventory items are by ID, and not by name, but I've not checked myself. ### External dependencies None.
adam added the type: featurepending closure labels 2025-12-29 20:38:58 +01:00
adam closed this issue 2025-12-29 20:38:58 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 15, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 15, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jan 14, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 14, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8619