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

Provide feature parity in module bay dropdown #11316

New Issue
Closed
opened 2025-12-29 21:43:33 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:43:33 +01:00
Owner
Copy Link

Originally created by @0lini on GitHub (Jun 23, 2025).

Originally assigned to: @pheus on GitHub.

NetBox version

v4.3.2

Feature type

New functionality

Proposed functionality

When assigning/creating a module on a device, currently there is no indication if a module bay is occupied or not. I propose a indication like with interfaces or front/rear ports, where bays in the drop down menu are grayed out and you are not able to select them.

Use case

When assign a lot of modules through the GUI to a device with a lot of module bays this will help the user by being able to see the which bays are already occupied and also not being able to select them.

Database changes

No response

External dependencies

No response

Originally created by @0lini on GitHub (Jun 23, 2025). Originally assigned to: @pheus on GitHub. ### NetBox version v4.3.2 ### Feature type New functionality ### Proposed functionality When assigning/creating a module on a device, currently there is no indication if a module bay is occupied or not. I propose a indication like with interfaces or front/rear ports, where bays in the drop down menu are grayed out and you are not able to select them. ### Use case When assign a lot of modules through the GUI to a device with a lot of module bays this will help the user by being able to see the which bays are already occupied and also not being able to select them. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:43:33 +01:00
adam closed this issue 2025-12-29 21:43:33 +01:00
adam commented 2025-12-29 21:43:34 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 25, 2025):

@0lini , thank you for your interest in extending NetBox. I think this is likely a useful addition.

Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jnovinger commented on GitHub (Jun 25, 2025): @0lini , thank you for your interest in extending NetBox. I think this is likely a useful addition. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:43:34 +01:00
Author
Owner
Copy Link

@0lini commented on GitHub (Jun 27, 2025):

I did a rewrite of the FR in simpler terms.

@0lini commented on GitHub (Jun 27, 2025): I did a rewrite of the FR in simpler terms.
adam commented 2025-12-29 21:43:34 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 30, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 30, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:43:34 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Oct 15, 2025):

I'd like to contribute this enhancement. Could you please assign the issue to me? Thanks!

@pheus commented on GitHub (Oct 15, 2025): I'd like to contribute this enhancement. Could you please assign the issue to me? Thanks!
adam commented 2025-12-29 21:43:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 15, 2025):

All yours @pheus!

@jeremystretch commented on GitHub (Oct 15, 2025): All yours @pheus!
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 complexity: low 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#11316
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?