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

netbox3.2-beta1 - Module bays Position rangeable #6107

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

Originally created by @PieterL75 on GitHub (Feb 16, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2-beta1

Feature type

Change to existing functionality

Proposed functionality

When creating a Module bays in a DeviceType, it is possible to use ranges in the name of the template.
The position however is a static field.

Enabling ranges for the Position field would allow us to create multiple bays in one go, with proper positions

Use case

Enabling ranges for the Position field would allow us to create multiple bays in one go, with proper positions

Ex: Name : FPC[0-5]
Position [0-5]

Database changes

None

External dependencies

None

Originally created by @PieterL75 on GitHub (Feb 16, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2-beta1 ### Feature type Change to existing functionality ### Proposed functionality When creating a Module bays in a DeviceType, it is possible to use ranges in the name of the template. The position however is a static field. Enabling ranges for the Position field would allow us to create multiple bays in one go, with proper positions ### Use case Enabling ranges for the Position field would allow us to create multiple bays in one go, with proper positions Ex: Name : FPC[0-5] Position [0-5] ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurebeta labels 2025-12-29 19:36:52 +01:00
adam closed this issue 2025-12-29 19:36:52 +01:00
adam commented 2025-12-29 19:36:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 17, 2022):

Admittedly, this is a shortcoming of the current implementation. The reason it's not yet supported is that it will likely require some tweaking of the bulk creation form logic.

@jeremystretch commented on GitHub (Feb 17, 2022): Admittedly, this is a shortcoming of the current implementation. The reason it's not yet supported is that it will likely require some tweaking of the bulk creation form logic.
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 beta 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#6107
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?