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

Option to edit a device directly out of the rack view #6969

New Issue
Closed
opened 2025-12-29 19:47:17 +01:00 by adam · 7 comments
adam commented 2025-12-29 19:47:17 +01:00
Owner
Copy Link

Originally created by @heiko-ma on GitHub (Sep 12, 2022).

NetBox version

v.3.3.2

Feature type

New functionality

Proposed functionality

When selecting device in a rack, the device overview is opened and the device must be edited via the corresponding button. After saving the changes, the user gets redirected back to the device overview.
When editing multiple devices in a rack (e.g. moving many patchpanels), this flow can be tedious as the user must navigate back to the rack every time.
It would be benificient if there would be a button beside the rack device which leads directly to the editing dialog and returns to the rack after editing
The flow would be like this:

  • Open rack "foo"
  • Edit the device "bar" via the button
  • Make the changes and click "save"
  • Get redirected back to rack "foo"

This can be achieved by inserting an identifier in the edit url which represents the rack id from which the request originated from:
/dcim/devices/1633/edit/?rack_id=80
Alternatively, the rack id can be retrieved through the device itself as it is linked with the rack.

This kind of flow could also be implemented for creating new devices.

Use case

This change would benefit the fluentness of editing a multiple devices in a rack as the user gets redirected to the rack every time and doesn't need to navigate back to it.

Database changes

No response

External dependencies

No response

Originally created by @heiko-ma on GitHub (Sep 12, 2022). ### NetBox version v.3.3.2 ### Feature type New functionality ### Proposed functionality When selecting device in a rack, the device overview is opened and the device must be edited via the corresponding button. After saving the changes, the user gets redirected back to the device overview. When editing multiple devices in a rack (e.g. moving many patchpanels), this flow can be tedious as the user must navigate back to the rack every time. It would be benificient if there would be a button beside the rack device which leads directly to the editing dialog and returns to the rack after editing The flow would be like this: - Open rack "foo" - Edit the device "bar" via the button - Make the changes and click "save" - Get redirected back to rack "foo" This can be achieved by inserting an identifier in the edit url which represents the rack id from which the request originated from: /dcim/devices/1633/edit/?rack_id=80 Alternatively, the rack id can be retrieved through the device itself as it is linked with the rack. This kind of flow could also be implemented for creating new devices. ### Use case This change would benefit the fluentness of editing a multiple devices in a rack as the user gets redirected to the rack every time and doesn't need to navigate back to it. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under reviewtopic: UI/UX labels 2025-12-29 19:47:17 +01:00
adam closed this issue 2025-12-29 19:47:17 +01:00
adam commented 2025-12-29 19:47:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 12, 2022):

It would be benificient if there would be a button beside the rack device which leads directly to the editing dialog and returns to the rack after editing

There are several challenges to this. First, where would you put the button? The rack elevations are already pretty crowded as-is. Second, you would need a mechanism to include the button only when appropriate. Rack elevations may be embedded on pages outside of NetBox (e.g. in a corporate wiki) where it would not make sense to display such controls.

When editing multiple devices in a rack (e.g. moving many patchpanels), this flow can be tedious as the user must navigate back to the rack every time.

Apologies if this sounds blunt, but why not just open the device view in a new browser tab each time?

@jeremystretch commented on GitHub (Sep 12, 2022): > It would be benificient if there would be a button beside the rack device which leads directly to the editing dialog and returns to the rack after editing There are several challenges to this. First, where would you put the button? The rack elevations are already pretty crowded as-is. Second, you would need a mechanism to include the button only when appropriate. Rack elevations may be embedded on pages outside of NetBox (e.g. in a corporate wiki) where it would not make sense to display such controls. > When editing multiple devices in a rack (e.g. moving many patchpanels), this flow can be tedious as the user must navigate back to the rack every time. Apologies if this sounds blunt, but why not just open the device view in a new browser tab each time?
adam commented 2025-12-29 19:47:19 +01:00
Author
Owner
Copy Link

@heiko-ma commented on GitHub (Sep 12, 2022):

There are several challenges to this. First, where would you put the button? The rack elevations are already pretty crowded as-is. Second, you would need a mechanism to include the button only when appropriate. Rack elevations may be embedded on pages outside of NetBox (e.g. in a corporate wiki) where it would not make sense to display such controls.

To clarify, I'm not talking about the rack elevations, you're right, it wouldn't make sense to display those controls there. I'm talking about the rack itself:
image

I think, it would be possible to display a button next to each height unit.

Apologies if this sounds blunt, but why not just open the device view in a new browser tab each time?

No worries, I can see where you're coming from, and in a normal desktop environment this procedure works just fine. Currently, we are testing out using netbox on android tablets in order to quicker document racks while on site. On android, navigation through those tabs can be quite a drag (especially when you have a ton of devices to edit) whereas the rest of the workflow is really smooth because you get redirected to the right page after each edit (e.g. connecting devices or creating interfaces). I hope this could clarify our approach and why i made this FR

@heiko-ma commented on GitHub (Sep 12, 2022): > There are several challenges to this. First, where would you put the button? The rack elevations are already pretty crowded as-is. Second, you would need a mechanism to include the button only when appropriate. Rack elevations may be embedded on pages outside of NetBox (e.g. in a corporate wiki) where it would not make sense to display such controls. To clarify, I'm not talking about the rack elevations, you're right, it wouldn't make sense to display those controls there. I'm talking about the rack itself: ![image](https://user-images.githubusercontent.com/64192965/189694563-36ff17fc-9d29-49bf-9ed9-bfd3c7c5991b.png) I think, it would be possible to display a button next to each height unit. > Apologies if this sounds blunt, but why not just open the device view in a new browser tab each time? No worries, I can see where you're coming from, and in a normal desktop environment this procedure works just fine. Currently, we are testing out using netbox on android tablets in order to quicker document racks while on site. On android, navigation through those tabs can be quite a drag (especially when you have a ton of devices to edit) whereas the rest of the workflow is really smooth because you get redirected to the right page after each edit (e.g. connecting devices or creating interfaces). I hope this could clarify our approach and why i made this FR
adam commented 2025-12-29 19:47:19 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Sep 12, 2022):

Just throwing ideas here, would it work if you were to be redirected back to the Rack elevation page when editing a device if you accessed said device from a Rack elevation ?

Something like this:
Rack Elevation page > Device > Device form -> Submit/Save -> Back to Rack Elevation page

@jsenecal commented on GitHub (Sep 12, 2022): Just throwing ideas here, would it work if you were to be redirected back to the Rack elevation page when editing a device if you accessed said device from a Rack elevation ? Something like this: `Rack Elevation` page > `Device `> `Device form` -> Submit/Save -> Back to `Rack Elevation` page
adam commented 2025-12-29 19:47:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 12, 2022):

To clarify, I'm not talking about the rack elevations, you're right, it wouldn't make sense to display those controls there. I'm talking about the rack itself:

When I say "elevations" I'm referring to the images on the righthand side of the screenshot you shared, showing the front and back of the rack. (We use the term "elevation" as in an architectural drawing showing a building as viewed from the street.) Is that what you're referring to?

@jeremystretch commented on GitHub (Sep 12, 2022): > To clarify, I'm not talking about the rack elevations, you're right, it wouldn't make sense to display those controls there. I'm talking about the rack itself: When I say "elevations" I'm referring to the images on the righthand side of the screenshot you shared, showing the front and back of the rack. (We use the term "elevation" as in an architectural drawing showing a building as viewed from the street.) Is that what you're referring to?
adam commented 2025-12-29 19:47:19 +01:00
Author
Owner
Copy Link

@heiko-ma commented on GitHub (Sep 12, 2022):

When I say "elevations" I'm referring to the images on the righthand side of the screenshot you shared, showing the front and back of the rack. (We use the term "elevation" as in an architectural drawing showing a building as viewed from the street.) Is that what you're referring to?

That is correct.

Just throwing ideas here, would it work if you were to be redirected back to the Rack elevation page when editing a device if you accessed said device from a Rack elevation ?

That was my first thought, though it would be a bit difficult to determine if the device was accessed via an elevation.

@heiko-ma commented on GitHub (Sep 12, 2022): > When I say "elevations" I'm referring to the images on the righthand side of the screenshot you shared, showing the front and back of the rack. (We use the term "elevation" as in an architectural drawing showing a building as viewed from the street.) Is that what you're referring to? That is correct. > Just throwing ideas here, would it work if you were to be redirected back to the Rack elevation page when editing a device if you accessed said device from a Rack elevation ? That was my first thought, though it would be a bit difficult to determine if the device was accessed via an elevation.
adam commented 2025-12-29 19:47:20 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 12, 2022):

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 (Nov 12, 2022): 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 19:47:20 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 13, 2022):

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 (Dec 13, 2022): 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 status: under review topic: UI/UX 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#6969
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?