starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Include the device as part of Change Log. #11236

New Issue
Closed
opened 2025-12-29 21:42:20 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:42:20 +01:00
Owner
Copy Link

Originally created by @CompPhy on GitHub (May 30, 2025).

NetBox version

v4.2.1

Feature type

Change to existing functionality

Proposed functionality

Add an additional breadcrumb to track the device, in addition to specific interface, power port, etc. in the Change Log.

Something like "Device -> Interface" as part of the Change Log object field? Or maybe add another field, similar to the user field, that tracks the device??

Use case

When doing an export from the change log screen, the "object" field only contains the specific endpoint (interface, power port, etc.) but not the actual device name. This makes it difficult to use exports for correlating changes across an entire device.

It is possible to click into the object through the UI, and see each device there, but it's kind of the same problem. For a large set of change logs this ends up resulting in a lot of click through to figure out which changes go to each high level device.

Database changes

Add additional field to the Change Log table???

External dependencies

No response

Originally created by @CompPhy on GitHub (May 30, 2025). ### NetBox version v4.2.1 ### Feature type Change to existing functionality ### Proposed functionality Add an additional breadcrumb to track the device, in addition to specific interface, power port, etc. in the Change Log. Something like "Device -> Interface" as part of the Change Log object field? Or maybe add another field, similar to the user field, that tracks the device?? ### Use case When doing an export from the change log screen, the "object" field only contains the specific endpoint (interface, power port, etc.) but not the actual device name. This makes it difficult to use exports for correlating changes across an entire device. It is possible to click into the object through the UI, and see each device there, but it's kind of the same problem. For a large set of change logs this ends up resulting in a lot of click through to figure out which changes go to each high level device. ### Database changes Add additional field to the Change Log table??? ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:42:20 +01:00
adam closed this issue 2025-12-29 21:42:20 +01:00
adam commented 2025-12-29 21:42:21 +01:00
Author
Owner
Copy Link

@CompPhy commented on GitHub (May 30, 2025):

I do understand that change log can also be seen by clicking over to individual devices, and this sort of gives us what we want. However, in this case we're trying to audit changes to multiple devices and having one export from Change Log sure would be nice.

@CompPhy commented on GitHub (May 30, 2025): I do understand that change log can also be seen by clicking over to individual devices, and this sort of gives us what we want. However, in this case we're trying to audit changes to multiple devices and having one export from Change Log sure would be nice.
adam commented 2025-12-29 21:42:21 +01:00
Author
Owner
Copy Link

@CompPhy commented on GitHub (May 30, 2025):

As an additional ask.... Currently Cable Termination doesn't have any click through breadcrumbs even on the UI. This makes it even harder for the click through type checks, because you have to look at each Request ID individually to get links to the objects.

@CompPhy commented on GitHub (May 30, 2025): As an additional ask.... Currently Cable Termination doesn't have any click through breadcrumbs even on the UI. This makes it even harder for the click through type checks, because you have to look at each Request ID individually to get links to the objects.
adam commented 2025-12-29 21:42:21 +01:00
Author
Owner
Copy Link

@CompPhy commented on GitHub (May 30, 2025):

I just realized, you actually don't see a Change Log when looking at the Device. You only see the top level device changes, and nothing for individual components. It sure would be nice if the device change log drilled down into the individual components to give a better view of all the changes that affect a given device.

@CompPhy commented on GitHub (May 30, 2025): I just realized, you actually don't see a Change Log when looking at the Device. You only see the top level device changes, and nothing for individual components. It sure would be nice if the device change log drilled down into the individual components to give a better view of all the changes that affect a given device.
adam commented 2025-12-29 21:42:22 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 30, 2025):

@CompPhy if I understand what you are looking for here if you have changed "interface1" then in object field you see "interface1" with a link to that interface, what you are asking for is for it to show the device or have another field that references the device?

I don't see this as practical for a number of reasons - first change logs are across all models so it's not clear what that related object would be (some cases it would be to a device, some to a parent object, etc.. I'm not sure that could be generic and would have to account for plugin objects as well.

Secondly the change logs are historical objects, so you would have to store just the name of the related object as the actual object could have been deleted. That is why there is no click through for a breadcrumb.

@arthanson commented on GitHub (May 30, 2025): @CompPhy if I understand what you are looking for here if you have changed "interface1" then in object field you see "interface1" with a link to that interface, what you are asking for is for it to show the device or have another field that references the device? I don't see this as practical for a number of reasons - first change logs are across all models so it's not clear what that related object would be (some cases it would be to a device, some to a parent object, etc.. I'm not sure that could be generic and would have to account for plugin objects as well. Secondly the change logs are historical objects, so you would have to store just the name of the related object as the actual object could have been deleted. That is why there is no click through for a breadcrumb.
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#11236
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?