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

Rack Face Not Auto Dropping Down #6666

New Issue
Closed
opened 2025-12-29 19:43:40 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:43:40 +01:00
Owner
Copy Link

Originally created by @dg2assassin on GitHub (Jul 14, 2022).

NetBox version

v3.2.6

Python version

3.8

Steps to Reproduce

  1. Create or edit a Device
  2. Select a rack
  3. Rack Face is skip, and Position becomes the next field to fill in

Expected Behavior

Once Rack has been filled in, Rack Face should be the next in the auto drop down list.

Observed Behavior

Rack Face is skipped, and Position becomes the next to fill in. If a new device is created, this field will be left blank while the other Location fields will be filled in. This could lead to the user confused why their device is not able to be created when everything looks correct.

Originally created by @dg2assassin on GitHub (Jul 14, 2022). ### NetBox version v3.2.6 ### Python version 3.8 ### Steps to Reproduce 1. Create or edit a Device 3. Select a rack 4. Rack Face is skip, and Position becomes the next field to fill in ### Expected Behavior Once Rack has been filled in, Rack Face should be the next in the auto drop down list. ### Observed Behavior Rack Face is skipped, and Position becomes the next to fill in. If a new device is created, this field will be left blank while the other Location fields will be filled in. This could lead to the user confused why their device is not able to be created when everything looks correct.
adam added the type: bugstatus: duplicate labels 2025-12-29 19:43:40 +01:00
adam closed this issue 2025-12-29 19:43:40 +01:00
adam commented 2025-12-29 19:43:41 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jul 15, 2022):

Same issue as #9734 - it's not intended that the next field is opened automatically at all.

While your report is older (missed it first time around), I'll close this in favor of the other one, as I already submitted the fix. Thanks for the report!

@kkthxbye-code commented on GitHub (Jul 15, 2022): Same issue as #9734 - it's not intended that the next field is opened automatically at all. While your report is older (missed it first time around), I'll close this in favor of the other one, as I already submitted the fix. Thanks for the report!
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 type: bug
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#6666
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?