Option to make new "Changelog message" field mandatory #1184

New Issue

MrUnknownDE · 2026-04-05T21:34:40+02:00

MrUnknownDE commented

2026-04-05 21:34:40 +02:00

Originally created by @RevLaw on 9/29/2025

NetBox version

v4.4.1

Feature type

Change to existing functionality

Proposed functionality

Hi NetBox team,

we would like to request an option to make the Changelog message field mandatory.
This would ensure that whenever a user makes a change in NetBox, they are required to provide a comment describing the modification.

This feature would help enforce better documentation and accountability for changes within the system, especially in collaborative environments.

Thank you for your amazing work on NetBox!

Use case

Enforces proper documentation for all changes, making it easier to understand the context of modifications.
Increases accountability by ensuring that users explicitly state the reason behind updates.
Improves collaboration across teams by providing consistent records and reducing ambiguity about why a change happened.
Makes auditing and troubleshooting easier, since the history of changes will always include human-readable explanations.

Database changes

No response

External dependencies

No response

*Originally created by @RevLaw on 9/29/2025* ### NetBox version v4.4.1 ### Feature type Change to existing functionality ### Proposed functionality Hi NetBox team, we would like to request an option to make the Changelog message field mandatory. This would ensure that whenever a user makes a change in NetBox, they are required to provide a comment describing the modification. This feature would help enforce better documentation and accountability for changes within the system, especially in collaborative environments. Thank you for your amazing work on NetBox! ### Use case - Enforces proper documentation for all changes, making it easier to understand the context of modifications. - Increases accountability by ensuring that users explicitly state the reason behind updates. - Improves collaboration across teams by providing consistent records and reducing ambiguity about why a change happened. - Makes auditing and troubleshooting easier, since the history of changes will always include human-readable explanations. ### Database changes _No response_ ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-05 21:34:40 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1184