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

Show cluster as mandatory when adding a virtual machine via UI #8680

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

Originally created by @empusas on GitHub (Sep 27, 2023).

NetBox version

v3.6.3

Python version

3.11

Steps to Reproduce

This is just a little cosmetic, but bothers me for a while. The Cluster is not shown as mandatory field in the VM creation form.

Expected Behavior

I would expect all mandatory fields marked bold and with a *

Observed Behavior

In the VM creation form the cluster seems like an optional field.

Originally created by @empusas on GitHub (Sep 27, 2023). ### NetBox version v3.6.3 ### Python version 3.11 ### Steps to Reproduce This is just a little cosmetic, but bothers me for a while. The Cluster is not shown as mandatory field in the VM creation form. ### Expected Behavior I would expect all mandatory fields marked bold and with a * ### Observed Behavior In the VM creation form the cluster seems like an optional field.
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:39:48 +01:00
adam closed this issue 2025-12-29 20:39:49 +01:00
adam commented 2025-12-29 20:39:50 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Sep 27, 2023):

It is a bit different in this case as either a site or cluster needs to be given (so cluster is optional if a site is given). Perhaps some help text under those fields stating that might be useful.

@arthanson commented on GitHub (Sep 27, 2023): It is a bit different in this case as either a site or cluster needs to be given (so cluster is optional if a site is given). Perhaps some help text under those fields stating that might be useful.
adam commented 2025-12-29 20:39:50 +01:00
Author
Owner
Copy Link

@empusas commented on GitHub (Sep 28, 2023):

agree, but this little change would help users to understand.

@empusas commented on GitHub (Sep 28, 2023): agree, but this little change would help users to understand.
adam commented 2025-12-29 20:39:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 2, 2023):

@empusas I think you misunderstood @arthanson's point. The cluser field is not mandatory for virtual machines, because a VM may be assigned to either a cluster or to a device. Displaying it as a mandatory field (akin to the name or status fields) would be misleading and confusing. So what specific change are you proposing?

(Also, reclassifying this as an enhancement as it's not a bug.)

@jeremystretch commented on GitHub (Oct 2, 2023): @empusas I think you misunderstood @arthanson's point. The cluser field is **not** mandatory for virtual machines, because a VM may be assigned to either a cluster _or_ to a device. Displaying it as a mandatory field (akin to the name or status fields) would be misleading and confusing. So what specific change are you proposing? (Also, reclassifying this as an enhancement as it's not a bug.)
adam commented 2025-12-29 20:39:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 6, 2023):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Nov 6, 2023): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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: revisions needed type: feature
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#8680
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?