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

Create devices without specifying a name #3228

New Issue
Closed
opened 2025-12-29 18:26:53 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:26:53 +01:00
Owner
Copy Link

Originally created by @marcelb98 on GitHub (Jan 26, 2020).

Environment

  • Python version: 3.7.6
  • NetBox version: a9ff06a6ee4e (v2.7.2)

Steps to Reproduce

  1. Create a rack
  2. Add a new device to the rack, without defining a name for the new device

Expected Behavior

Since the name for devices is not marked as a mandatory field, it should be possible to create a device without specifying a name.
grafik

For some devices (e.g. cable routing) the name is irrelevant, the only necessary information is the existence of the device. The name of the corresponding device type could be used for the name of the device.

This was possible in previous versions of Netbox.

Observed Behavior

Submitting the form without specifying a device name results in an error:
grafik

Typing in the name of the device type manually isn't a fix since it would be only possible to create a single device of this type with the name of the type.

Originally created by @marcelb98 on GitHub (Jan 26, 2020). ### Environment * Python version: 3.7.6 * NetBox version: a9ff06a6ee4e (v2.7.2) <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Create a rack 2. Add a new device to the rack, without defining a name for the new device <!-- What did you expect to happen? --> ### Expected Behavior Since the name for devices is not marked as a mandatory field, it should be possible to create a device without specifying a name. ![grafik](https://user-images.githubusercontent.com/20777899/73141857-dc103100-4088-11ea-9353-b5d862e50f57.png) For some devices (e.g. cable routing) the name is irrelevant, the only necessary information is the existence of the device. The name of the corresponding device type could be used for the name of the device. This was possible in previous versions of Netbox. <!-- What happened instead? --> ### Observed Behavior Submitting the form without specifying a device name results in an error: ![grafik](https://user-images.githubusercontent.com/20777899/73141911-71132a00-4089-11ea-97b5-2829b97499aa.png) Typing in the name of the device type manually isn't a fix since it would be only possible to create a single device of this type with the name of the type.
adam added the status: duplicate label 2025-12-29 18:26:53 +01:00
adam closed this issue 2025-12-29 18:26:53 +01:00
adam commented 2025-12-29 18:26:54 +01:00
Author
Owner
Copy Link

@hSaria commented on GitHub (Jan 27, 2020):

This was fixed in #3983 which will be included in the next version of NetBox (v2.7.3).

@hSaria commented on GitHub (Jan 27, 2020): This was fixed in #3983 which will be included in the next version of NetBox (v2.7.3).
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 status: duplicate
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#3228
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?