Make serial numbers unique #4002

Closed
opened 2025-12-29 18:32:33 +01:00 by adam · 1 comment
Owner

Originally created by @proudbro on GitHub (Aug 20, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.8.9

Proposed Functionality

Please make it possible to use unique serial numbers for Devices as asset tag. Both should be unique

Use Case

At the moment we can create two different devices with the same serial numbers, in contrast to asset tag. In some cases, this can contribute to the creation of duplicates in the system.

Database Changes

External Dependencies

Originally created by @proudbro on GitHub (Aug 20, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.9 * NetBox version: 2.8.9 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Please make it possible to use unique serial numbers for Devices as asset tag. Both should be unique <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case At the moment we can create two different devices with the same serial numbers, in contrast to asset tag. In some cases, this can contribute to the creation of duplicates in the system. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam closed this issue 2025-12-29 18:32:33 +01:00
Author
Owner

@jeremystretch commented on GitHub (Aug 20, 2020):

Uniqueness is intentionally not enforced for device serial numbers as they cannot be guaranteed to be unique, even within the scope of a specific device type. You can find discussion around this in old issues. (Uniqueness of the asset tag is enforced because its namespace is controlled by the NetBox owner.)

@jeremystretch commented on GitHub (Aug 20, 2020): Uniqueness is intentionally not enforced for device serial numbers as they cannot be guaranteed to be unique, even within the scope of a specific device type. You can find discussion around this in old issues. (Uniqueness of the asset tag is enforced because its namespace is controlled by the NetBox owner.)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4002