Add changelog message support to bulk creation of IP addresses #56

New Issue

MrUnknownDE · 2026-04-05T16:21:22+02:00

MrUnknownDE commented

2026-04-05 16:21:22 +02:00

Originally created by @pheus on 3/30/2026

NetBox version

v4.5.5

Feature type

Change to existing functionality

Proposed functionality

NetBox currently allows a changelog message to be entered when creating a single IP address, but not when creating IP addresses via the bulk creation workflow. I would like to propose adding changelog message support to bulk IP address creation so that the workflow is consistent with single-object creation.

From an implementation perspective, this should be handled in the shared bulk-create workflow rather than only at the IPAM view level. The bulk create UI should expose the changelog message field from the underlying model form, and the submitted value should be applied to each object created from the expanded pattern. This would ensure that every created IP address records the same changelog context, just as users would expect when creating objects individually.

Use case

When creating IP addresses in bulk, users often need to record why those addresses were added, for example for a customer rollout, migration, reservation, or change request. Today, that context can be captured when creating one object at a time, but it is lost when using bulk creation.

Adding changelog message support to bulk creation would make the workflow more consistent, improve auditability, and reduce the need for manual follow-up edits just to document why a group of objects was created.

Database changes

None.

External dependencies

None.

*Originally created by @pheus on 3/30/2026* ### NetBox version v4.5.5 ### Feature type Change to existing functionality ### Proposed functionality NetBox currently allows a changelog message to be entered when creating a single IP address, but not when creating IP addresses via the bulk creation workflow. I would like to propose adding changelog message support to bulk IP address creation so that the workflow is consistent with single-object creation. From an implementation perspective, this should be handled in the shared bulk-create workflow rather than only at the IPAM view level. The bulk create UI should expose the changelog message field from the underlying model form, and the submitted value should be applied to each object created from the expanded pattern. This would ensure that every created IP address records the same changelog context, just as users would expect when creating objects individually. ### Use case When creating IP addresses in bulk, users often need to record why those addresses were added, for example for a customer rollout, migration, reservation, or change request. Today, that context can be captured when creating one object at a time, but it is lost when using bulk creation. Adding changelog message support to bulk creation would make the workflow more consistent, improve auditability, and reduce the need for manual follow-up edits just to document why a group of objects was created. ### Database changes None. ### External dependencies None.

MrUnknownDE added the status: accepted netbox status: accepted status: accepted complexity: medium status: accepted type: feature status: accepted status: accepted status: accepted status: accepted status: accepted netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox type: feature type: feature type: feature type: feature type: feature type: feature type: feature complexity: medium labels 2026-04-05 16:21:23 +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 complexity: medium complexity: medium netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted 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#56