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

Color of front and rear ports not nullable on bulk edit #7288

New Issue
Closed
opened 2025-12-29 20:21:20 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:21:20 +01:00
Owner
Copy Link

Originally created by @phurrelmann on GitHub (Nov 25, 2022).

Originally assigned to: @phurrelmann on GitHub.

NetBox version

V3.3.5

Python version

3.9

Steps to Reproduce

Colors defined on front and rearports are not nullable on bulk edit.

  1. Create more than 2 front or rear ports
  2. Select 2 or more front or rear ports and do a bulk edit
  3. Color can be changed but not cleared

I can prepare a PR, if accepted

Expected Behavior

Color field on bulk edit of front and rear ports should be nullable and the checkbox "Set Null" is visible

Observed Behavior

Color field on bulk edit of front and rear ports are not nullable. The check box "Set Null" is missing

Originally created by @phurrelmann on GitHub (Nov 25, 2022). Originally assigned to: @phurrelmann on GitHub. ### NetBox version V3.3.5 ### Python version 3.9 ### Steps to Reproduce Colors defined on front and rearports are not nullable on bulk edit. 1. Create more than 2 front or rear ports 2. Select 2 or more front or rear ports and do a bulk edit 3. Color can be changed but not cleared I can prepare a PR, if accepted ### Expected Behavior Color field on bulk edit of front and rear ports should be nullable and the checkbox "Set Null" is visible ### Observed Behavior Color field on bulk edit of front and rear ports are not nullable. The check box "Set Null" is missing
adam added the type: bugstatus: accepted labels 2025-12-29 20:21:20 +01:00
adam closed this issue 2025-12-29 20:21:24 +01:00
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 status: accepted type: bug
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#7288
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?