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

Highlight only custom fields that have changed in change log #7916

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

Originally created by @decoupca on GitHub (Apr 17, 2023).

NetBox version

v3.4.8

Feature type

Change to existing functionality

Proposed functionality

Currently, changes to any custom field highlights all custom fields in the diff. This makes drilling down exactly what changed difficult, especially for objects with many custom fields. I propose to modify behavior so only changed custom fields are highlighted.

Use case

  • For objects with many custom fields, the current diff and highlight behavior makes it hard to see at a glance which custom field (or fields) have changed. Highlighting only those that have changed will make this easier, and is more semantic—it's counter-intuitive to highlight any item in a diff that hasn't actually changed.

Database changes

No response

External dependencies

No response

Originally created by @decoupca on GitHub (Apr 17, 2023). ### NetBox version v3.4.8 ### Feature type Change to existing functionality ### Proposed functionality Currently, changes to any custom field highlights all custom fields in the diff. This makes drilling down exactly what changed difficult, especially for objects with many custom fields. I propose to modify behavior so only changed custom fields are highlighted. ### Use case - For objects with many custom fields, the current diff and highlight behavior makes it hard to see at a glance which custom field (or fields) have changed. Highlighting only those that have changed will make this easier, and is more semantic—it's counter-intuitive to highlight any item in a diff that hasn't actually changed. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:29:57 +01:00
adam closed this issue 2025-12-29 20:29:57 +01:00
adam commented 2025-12-29 20:29:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 17, 2023):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #10924 for further discussion.

@jeremystretch commented on GitHub (Apr 17, 2023): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #10924 for further discussion.
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#7916
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?