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

Additional Fields in Device Bay Table #6239

New Issue
Closed
opened 2025-12-29 19:38:24 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:38:24 +01:00
Owner
Copy Link

Originally created by @johannwagner on GitHub (Mar 21, 2022).

Originally assigned to: @minitriga on GitHub.

NetBox version

v3.1.6

Feature type

New functionality

Proposed functionality

We would like to see additional fields within the Device Bays table. In particular, we want to introduce the following fields:

  • Device Type
  • Device Role

We are also happy to provide the needed PR for this feature!

Screenshot from 2022-03-21 12-36-24

Use case

We use housings for some devices, which have different types and roles. Therefore a housing can contain various different device types and roles. In the device bay overview, we cannot view the different types and roles within the housing. This results in each device having to be viewed individually to see the type and/or role of the device. We want to resolve this problem to provide a better user experience.

Database changes

None

External dependencies

None

Originally created by @johannwagner on GitHub (Mar 21, 2022). Originally assigned to: @minitriga on GitHub. ### NetBox version v3.1.6 ### Feature type New functionality ### Proposed functionality We would like to see additional fields within the Device Bays table. In particular, we want to introduce the following fields: - Device Type - Device Role We are also happy to provide the needed PR for this feature! ![Screenshot from 2022-03-21 12-36-24](https://user-images.githubusercontent.com/12380026/159253889-a6a95317-45c3-424f-9739-41600516e7b2.png) ### Use case We use housings for some devices, which have different types and roles. Therefore a housing can contain various different device types and roles. In the device bay overview, we cannot view the different types and roles within the housing. This results in each device having to be viewed individually to see the type and/or role of the device. We want to resolve this problem to provide a better user experience. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:38:24 +01:00
adam closed this issue 2025-12-29 19:38:24 +01:00
adam commented 2025-12-29 19:38:25 +01:00
Author
Owner
Copy Link

@minitriga commented on GitHub (Mar 25, 2022):

PR Open

@minitriga commented on GitHub (Mar 25, 2022): PR Open
adam commented 2025-12-29 19:38:25 +01:00
Author
Owner
Copy Link

@johannwagner commented on GitHub (Mar 28, 2022):

Thanks a lot!

@johannwagner commented on GitHub (Mar 28, 2022): Thanks a lot!
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: accepted 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#6239
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?