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

Create and Add Another fills description with previous entries #5526

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

Originally created by @sieuwe on GitHub (Oct 18, 2021).

NetBox version

v3.0.7

Python version

3.8

Steps to Reproduce

  1. Create IP range
  2. Enter IP range data including description
  3. Choose 'Create & Add Another'

Expected Behavior

Description should stay empty.

Observed Behavior

Description of new IP Range get's filled with previous Description
If you change the description and click 'Create & Add Another' again, the next one gets filled with ['Description IP range 1', 'Description IP range 2']

Originally created by @sieuwe on GitHub (Oct 18, 2021). ### NetBox version v3.0.7 ### Python version 3.8 ### Steps to Reproduce 1. Create IP range 2. Enter IP range data including description 3. Choose 'Create & Add Another' ### Expected Behavior Description should stay empty. ### Observed Behavior Description of new IP Range get's filled with previous Description If you change the description and click 'Create & Add Another' again, the next one gets filled with ['_Description IP range 1_', '_Description IP range 2_']
adam closed this issue 2025-12-29 19:29:00 +01:00
adam commented 2025-12-29 19:29:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 18, 2021):

Description should stay empty.

It is expected that the description will be replicated when cloning an IP range, just as it is for other models which have a description field (circuits, locations, IP addresses, etc.). Granted this is subjective, however the current behavior is consistent with how this feature has always functioned.

@jeremystretch commented on GitHub (Oct 18, 2021): > Description should stay empty. It is expected that the description will be replicated when cloning an IP range, just as it is for other models which have a description field (circuits, locations, IP addresses, etc.). Granted this is subjective, however the current behavior is consistent with how this feature has always functioned.
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
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#5526
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?