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 a human readable summary column to updated changelogs #9806

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

Originally created by @ITJamie on GitHub (Jun 6, 2024).

Originally assigned to: @jeffgdotorg on GitHub.

NetBox version

v4.0.3

Feature type

Data model extension

Proposed functionality

Addition of a read-only text field containing an autogenerated string of a high-level list of changes in that changelog.
examples of summarys:

  • Name and Custom field X,Y & Z updated
  • Primary IP assigned
  • Name Updated, OOB IP assigned
  • Tags removed

Use case

when looking at an object with a large list of updated changelogs it can take a while to track down the specific change you're looking for.
Having a quick summary text field that had a human-readable list of high-level changes that happened in that update would be fantastic to limit the amount of individual changelogs you need to look at when trying to find a specific change event

This was flagged to me by a staff member who pointed out that the change-logs in our old system(racktables) had a summary view of what fields changed in a changelog event which made it easier to track down a specific change without looking through potentially hundreds of updated changelog entrys on an object

Database changes

a text field to store the "summary" if we choose to store the value rather than generate on the fly

External dependencies

N/A

Originally created by @ITJamie on GitHub (Jun 6, 2024). Originally assigned to: @jeffgdotorg on GitHub. ### NetBox version v4.0.3 ### Feature type Data model extension ### Proposed functionality Addition of a read-only text field containing an autogenerated string of a high-level list of changes in that changelog. examples of summarys: - `Name and Custom field X,Y & Z updated` - `Primary IP assigned` - `Name Updated, OOB IP assigned` - `Tags removed` ### Use case when looking at an object with a large list of `updated` changelogs it can take a while to track down the specific change you're looking for. Having a quick `summary` text field that had a human-readable list of high-level changes that happened in that update would be fantastic to limit the amount of individual changelogs you need to look at when trying to find a specific change event This was flagged to me by a staff member who pointed out that the change-logs in our old system(racktables) had a summary view of what fields changed in a changelog event which made it easier to track down a specific change without looking through potentially hundreds of `updated` changelog entrys on an object ### Database changes a text field to store the "summary" if we choose to store the value rather than generate on the fly ### External dependencies N/A
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:22:57 +01:00
adam closed this issue 2025-12-29 21:22:57 +01:00
adam commented 2025-12-29 21:22:58 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Jun 10, 2024):

I'd like to understand the comparative use case a little better. Could you please link me to a place in the racktables demo where I can see the feature that inspired this FR? I spent a few minutes looking for it, but it's eluding me.

@jeffgdotorg commented on GitHub (Jun 10, 2024): I'd like to understand the comparative use case a little better. Could you please link me to a place in the [racktables demo](https://demo.racktables.org/) where I can see the feature that inspired this FR? I spent a few minutes looking for it, but it's eluding me.
adam commented 2025-12-29 21:22:59 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Jun 11, 2024):

apologies. it turns out that the extra log items were a custom extension in racktables that a previous staff member had made rather than a native function of racktables.
it is still quite a useful feature request to have a quick summary of the fileld names where the value changed on each change request.

@ITJamie commented on GitHub (Jun 11, 2024): apologies. it turns out that the extra log items were a custom extension in racktables that a previous staff member had made rather than a native function of racktables. it is still quite a useful feature request to have a quick summary of the fileld names where the value changed on each change request.
adam commented 2025-12-29 21:22:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 19, 2024):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Jun 19, 2024): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:23:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 26, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jun 26, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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: revisions needed 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#9806
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?