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

Redirect back to rack view when deleting a device #6448

New Issue
Closed
opened 2025-12-29 19:40:51 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:40:51 +01:00
Owner
Copy Link

Originally created by @jasonyates on GitHub (May 5, 2022).

NetBox version

3.2.2

Feature type

Change to existing functionality

Proposed functionality

When looking at the rack view and subsequently deleting a device, redirect back to the rack view after deletion.

Currently if you navigate from the device view to a device and then delete said device, you are redirected to the full device list and it takes several clicks to get back to the rack view. It would speed up using Netbox if you were redirected back to the rack view.

Use case

We use Netbox on an iPad to physically audit racks, sometimes it's required to delete a device from Netbox. When doing so you are redirected back to the full device list meaning you either have to hit the back button several times to get back to the rack view or navigate to / search for the rack again to get back to where you were.

Database changes

No response

External dependencies

No response

Originally created by @jasonyates on GitHub (May 5, 2022). ### NetBox version 3.2.2 ### Feature type Change to existing functionality ### Proposed functionality When looking at the rack view and subsequently deleting a device, redirect back to the rack view after deletion. Currently if you navigate from the device view to a device and then delete said device, you are redirected to the full device list and it takes several clicks to get back to the rack view. It would speed up using Netbox if you were redirected back to the rack view. ### Use case We use Netbox on an iPad to physically audit racks, sometimes it's required to delete a device from Netbox. When doing so you are redirected back to the full device list meaning you either have to hit the back button several times to get back to the rack view or navigate to / search for the rack again to get back to where you were. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:40:51 +01:00
adam closed this issue 2025-12-29 19:40:51 +01:00
adam commented 2025-12-29 19:40:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 5, 2022):

We can only control the post-deletion redirect URL across one "click," by appending the return_url parameter to the URL. Without this, the default return URL (typically the objects list) will be used.

@jeremystretch commented on GitHub (May 5, 2022): We can only control the post-deletion redirect URL across one "click," by appending the `return_url` parameter to the URL. Without this, the default return URL (typically the objects list) will be used.
adam commented 2025-12-29 19:40:51 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (May 5, 2022):

Could it be an option to add the actions menu from device table onto the rack view? That way you could delete, edit, etc and get the return url set

On 5 May 2022, at 16:34, Jeremy Stretch @.***> wrote:


We can only control the post-deletion redirect URL across one "click," by appending the return_url parameter to the URL. Without this, the default return URL (typically the objects list) will be used.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

@hagbarddenstore commented on GitHub (May 5, 2022): Could it be an option to add the actions menu from device table onto the rack view? That way you could delete, edit, etc and get the return url set > On 5 May 2022, at 16:34, Jeremy Stretch ***@***.***> wrote: > >  > We can only control the post-deletion redirect URL across one "click," by appending the return_url parameter to the URL. Without this, the default return URL (typically the objects list) will be used. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you are subscribed to this thread.
adam commented 2025-12-29 19:40:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 6, 2022):

@hagbarddenstore that's not really feasible: The rack elevations are rendered as embedded SVG documents. I mean I'm sure it's possible with enough front end code but it's not going to be worth the effort required.

@jeremystretch commented on GitHub (May 6, 2022): @hagbarddenstore that's not really feasible: The rack elevations are rendered as embedded SVG documents. I mean I'm sure it's possible with enough front end code but it's not going to be worth the effort required.
adam commented 2025-12-29 19:40:52 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (May 6, 2022):

Ah right, forgot about that bit.

Sent from my iPhone

On 6 May 2022, at 15:50, Jeremy Stretch @.***> wrote:


@hagbarddenstore that's not really feasible: The rack elevations are rendered as embedded SVG documents. I mean I'm sure it's possible with enough front end code but it's not going to be worth the effort required.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

@hagbarddenstore commented on GitHub (May 6, 2022): Ah right, forgot about that bit. Sent from my iPhone > On 6 May 2022, at 15:50, Jeremy Stretch ***@***.***> wrote: > >  > @hagbarddenstore that's not really feasible: The rack elevations are rendered as embedded SVG documents. I mean I'm sure it's possible with enough front end code but it's not going to be worth the effort required. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you were mentioned.
adam commented 2025-12-29 19:40:52 +01:00
Author
Owner
Copy Link

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

Absent any technical solution per my comment above, I'm going to close this out. Happy to revisit if someone has a feasible implementation to propose.

@jeremystretch commented on GitHub (May 12, 2022): Absent any technical solution per my comment above, I'm going to close this out. Happy to revisit if someone has a feasible implementation to propose.
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 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#6448
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?