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

When adding a device from Rack Elevation add a list of devices to choose from #1195

New Issue
Closed
opened 2025-12-29 16:29:57 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:29:57 +01:00
Owner
Copy Link

Originally created by @traveler3468 on GitHub (Aug 24, 2017).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7
  • NetBox version: 2.1.2

Description

I was thinking that it would be nice to have the ability to select from existing devices in NetBox when adding a device from the rack elevations view. I think the devices would show up in a drop down list and be filtered based in the tenant/site that the rack belongs too. This would allow for devices to be created and tracked in NetBox before they were racked and also allow the ease at which devices are added to the rack space.

Thoughts?

Originally created by @traveler3468 on GitHub (Aug 24, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### Issue type [x] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * Python version: 2.7 * NetBox version: 2.1.2 <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description I was thinking that it would be nice to have the ability to select from existing devices in NetBox when adding a device from the rack elevations view. I think the devices would show up in a drop down list and be filtered based in the tenant/site that the rack belongs too. This would allow for devices to be created and tracked in NetBox before they were racked and also allow the ease at which devices are added to the rack space. Thoughts?
adam closed this issue 2025-12-29 16:29:57 +01:00
adam commented 2025-12-29 16:29:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 29, 2017):

How specifically would you implement this? Could you mock up some screenshots?

@jeremystretch commented on GitHub (Aug 29, 2017): How specifically would you implement this? Could you mock up some screenshots?
adam commented 2025-12-29 16:29:58 +01:00
Author
Owner
Copy Link

@cslingerland commented on GitHub (Aug 30, 2017):

addexistingdevice

Here's what I mocked up. It's probably the sloppiest way of doing it, but it gets the job done. I've attached the files I edited as well.
/dcim/views.py
views (1).txt
/templates/dcim/rack.html
rack.txt

I've got it working by calling to the API via ajax. I've attached the updated rack.html file here. Sorry for the txt files, I can't upload html files and I'm awful with git so I don't know how to submit it that way.
rack (1).txt

@cslingerland commented on GitHub (Aug 30, 2017): ![addexistingdevice](https://user-images.githubusercontent.com/2353683/29892576-197ad816-8d9d-11e7-8802-34ab6e19f41b.png) Here's what I mocked up. It's probably the sloppiest way of doing it, but it gets the job done. I've attached the files I edited as well. /dcim/views.py [views (1).txt](https://github.com/digitalocean/netbox/files/1264965/views.1.txt) /templates/dcim/rack.html [rack.txt](https://github.com/digitalocean/netbox/files/1264934/rack.txt) I've got it working by calling to the API via ajax. I've attached the updated rack.html file here. Sorry for the txt files, I can't upload html files and I'm awful with git so I don't know how to submit it that way. [rack (1).txt](https://github.com/digitalocean/netbox/files/1265237/rack.1.txt)
adam commented 2025-12-29 16:29:59 +01:00
Author
Owner
Copy Link

@cslingerland commented on GitHub (Sep 21, 2017):

What do you think? Is there anything else that we can provide on this request?

@cslingerland commented on GitHub (Sep 21, 2017): What do you think? Is there anything else that we can provide on this request?
adam commented 2025-12-29 16:29:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 25, 2017):

To be honest this feels very redundant. There's negligible gain over just editing the device and selecting the desired face face and position there.

@jeremystretch commented on GitHub (Sep 25, 2017): To be honest this feels very redundant. There's negligible gain over just editing the device and selecting the desired face face and position there.
adam commented 2025-12-29 16:29:59 +01:00
Author
Owner
Copy Link

@cslingerland commented on GitHub (Sep 25, 2017):

I can see where you're coming from. Where I see the value here is with a new implementation of NetBox where you import a bunch of devices (i.e. a list of devices in a datacenter) that need to then be put into rack assignments. Going back and pulling up every device, choosing edit, and placing it in the rack is a lot more time consuming than just pulling up the rack and placing all the devices where they need to be.

That's the thinking behind this one, but I can certainly see your perspective and not wanting to add it.

@cslingerland commented on GitHub (Sep 25, 2017): I can see where you're coming from. Where I see the value here is with a new implementation of NetBox where you import a bunch of devices (i.e. a list of devices in a datacenter) that need to then be put into rack assignments. Going back and pulling up every device, choosing edit, and placing it in the rack is a lot more time consuming than just pulling up the rack and placing all the devices where they need to be. That's the thinking behind this one, but I can certainly see your perspective and not wanting to add it.
adam commented 2025-12-29 16:29:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 20, 2017):

Might revisit this at some point but it's unlikely to get any attention in the near future.

@jeremystretch commented on GitHub (Oct 20, 2017): Might revisit this at some point but it's unlikely to get any attention in the near future.
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
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#1195
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?