starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add an asset tag field for devices #323

New Issue
Closed
opened 2025-12-29 16:20:56 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:20:56 +01:00
Owner
Copy Link

Originally created by @NetBod on GitHub (Aug 3, 2016).

Hi, I've been trying netbox out for a few weeks now and its looking good and coming along nicely. One of the things that is missing for me is a field to put the device asset Tag details in, where I work everything gets tagged with a unique value, number and letters, it would be nice to be able to add this to the device in netbox to complete its details. I did a quick search but could see if this had been suggested before or maybe its already there and I'm just missing something.... :-)
Thanks
Tim

Originally created by @NetBod on GitHub (Aug 3, 2016). Hi, I've been trying netbox out for a few weeks now and its looking good and coming along nicely. One of the things that is missing for me is a field to put the device asset Tag details in, where I work everything gets tagged with a unique value, number and letters, it would be nice to be able to add this to the device in netbox to complete its details. I did a quick search but could see if this had been suggested before or maybe its already there and I'm just missing something.... :-) Thanks Tim
adam closed this issue 2025-12-29 16:20:56 +01:00
adam commented 2025-12-29 16:20:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2016):

This is something that would be addressed by #129 (custom fields). I'd imagine it's a common enough requirement to justify adding a built-in field to the Device model, but I'll let others weigh in.

@jeremystretch commented on GitHub (Aug 3, 2016): This is something that would be addressed by #129 (custom fields). I'd imagine it's a common enough requirement to justify adding a built-in field to the Device model, but I'll let others weigh in.
adam commented 2025-12-29 16:20:56 +01:00
Author
Owner
Copy Link

@csfreak commented on GitHub (Aug 3, 2016):

Maybe the middle ground would be to have the initial_data load an asset tag field, then those that dont want it can easily remove it.

Edit: spelling

@csfreak commented on GitHub (Aug 3, 2016): Maybe the middle ground would be to have the initial_data load an asset tag field, then those that dont want it can easily remove it. Edit: spelling
adam commented 2025-12-29 16:20:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2016):

@csfreak Each field of the model is actually a discrete column in the SQL table. The initial data just populates some rows as a convenience for new users.

@jeremystretch commented on GitHub (Aug 3, 2016): @csfreak Each field of the model is actually a discrete column in the SQL table. The initial data just populates some rows as a convenience for new users.
adam commented 2025-12-29 16:20:57 +01:00
Author
Owner
Copy Link

@robclarkey commented on GitHub (Aug 9, 2016):

+1 for this.

And expanding on this slightly... A dedicated view for searching only by the asset tag? Think this would be useful for those who have barcode scanners, to scan asset tags. Returning the information in the "Device" table on "/dcim/devices/xx" would be great for checking the device is in the right place.

@robclarkey commented on GitHub (Aug 9, 2016): +1 for this. And expanding on this slightly... A dedicated view for searching only by the asset tag? Think this would be useful for those who have barcode scanners, to scan asset tags. Returning the information in the "Device" table on "/dcim/devices/xx" would be great for checking the device is in the right place.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#323
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?