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

Add Additional Method of Assigning Devices to Racks #8212

New Issue
Closed
opened 2025-12-29 20:33:52 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:33:52 +01:00
Owner
Copy Link

Originally created by @adparis99 on GitHub (Jun 19, 2023).

NetBox version

v3.5.1

Feature type

Change to existing functionality

Proposed functionality

This feature request is somewhat of a piggyback off of FR #8552, specifically the second point. Currently, the only method of adding a device to a rack via the GUI is to navigate to the device and update the relevant rack properties. This feature would add the ability to add a device to a rack via the link presented on open rack spots.

Some comments were made on that FR and it's corresponding PR (#8876) that getting away from the current methodology of how IP addresses are able to be created/assigned is necessary, and that any feature along the lines of what I'm proposing would need to follow suit. Unfortunately, I'm not sure what would be needed to get away from the current workflow, but I'm hoping this request might spawn some healthy discussions on the matter.

Use case

Adding this functionality would make adding devices to racks via the GUI much simpler. Instead of having to individually update devices when creating new racks, a user could simply fill in a rack from the elevation page.

Database changes

None

External dependencies

None

Originally created by @adparis99 on GitHub (Jun 19, 2023). ### NetBox version v3.5.1 ### Feature type Change to existing functionality ### Proposed functionality This feature request is somewhat of a piggyback off of FR #8552, specifically the second point. Currently, the only method of adding a device to a rack via the GUI is to navigate to the device and update the relevant rack properties. This feature would add the ability to add a device to a rack via the link presented on open rack spots. Some comments were made on that FR and it's corresponding PR (#8876) that getting away from the current methodology of how IP addresses are able to be created/assigned is necessary, and that any feature along the lines of what I'm proposing would need to follow suit. Unfortunately, I'm not sure what would be needed to get away from the current workflow, but I'm hoping this request might spawn some healthy discussions on the matter. ### Use case Adding this functionality would make adding devices to racks via the GUI much simpler. Instead of having to individually update devices when creating new racks, a user could simply fill in a rack from the elevation page. ### Database changes None ### External dependencies None
adam added the type: featurepending closure labels 2025-12-29 20:33:52 +01:00
adam closed this issue 2025-12-29 20:33:52 +01:00
adam commented 2025-12-29 20:33:52 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 18, 2023):

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 18, 2023): 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/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:33:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 18, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 18, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#8212
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?