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

Changelog view "Difference" of custom_fields shouild only show changed custom_fields instead of the whole dict "changed" #8115

New Issue
Closed
opened 2025-12-29 20:32:36 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:32:36 +01:00
Owner
Copy Link

Originally created by @MalfuncEddie on GitHub (May 25, 2023).

NetBox version

v3.3.5

Feature type

Change to existing functionality

Proposed functionality

When a custom field is changed the changelog shows the entire dict of custom_fields is marked as changed. This is correct but it would be nice to have a diff of the custom_fields instead of the whole updated dict.

Work around is copy paste the dicts to https://www.jsondiff.com/

Use case

When having a lot of custom_fields it is not quite visible what has been changed.

Database changes

None

External dependencies

None,

Originally created by @MalfuncEddie on GitHub (May 25, 2023). ### NetBox version v3.3.5 ### Feature type Change to existing functionality ### Proposed functionality When a custom field is changed the changelog shows the entire dict of custom_fields is marked as changed. This is correct but it would be nice to have a diff of the custom_fields instead of the whole updated dict. Work around is copy paste the dicts to https://www.jsondiff.com/ ### Use case When having a lot of custom_fields it is not quite visible what has been changed. ### Database changes None ### External dependencies None,
adam added the type: feature label 2025-12-29 20:32:36 +01:00
adam closed this issue 2025-12-29 20:32:37 +01:00
adam commented 2025-12-29 20:32:37 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (May 25, 2023):

This seems like it's captured by https://github.com/netbox-community/netbox/issues/10924, which proposes the same idea but for the entire diff body.

@abhi1693 commented on GitHub (May 25, 2023): This seems like it's captured by https://github.com/netbox-community/netbox/issues/10924, which proposes the same idea but for the entire diff body.
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#8115
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?