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

deleted custom fields still visible as available table columns #5394

New Issue
Closed
opened 2025-12-29 19:27:26 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:27:26 +01:00
Owner
Copy Link

Originally created by @opericgithub on GitHub (Sep 20, 2021).

NetBox version

v2.11.11

Python version

3.7

Steps to Reproduce

  1. in the netbox administration section (admin/extras/customfield) create multiselect custom field and make it applicable to dcim>devices
  2. edit any device by selecting any value for the custom field
  3. delete newly created custom field
  4. go to devices->devices page
  5. go to table configuration parameters (configure button in the upper right corner)
  6. check the available colums

Expected Behavior

one should not expect custom field, that was previously deleted, to appear under "available columns"

Observed Behavior

custom field, that was previously deleted, appears under "available columns".

Originally created by @opericgithub on GitHub (Sep 20, 2021). ### NetBox version v2.11.11 ### Python version 3.7 ### Steps to Reproduce 1. in the netbox administration section (admin/extras/customfield) create multiselect custom field and make it applicable to dcim>devices 2. edit any device by selecting any value for the custom field 3. delete newly created custom field 4. go to devices->devices page 5. go to table configuration parameters (configure button in the upper right corner) 6. check the available colums ### Expected Behavior one should not expect custom field, that was previously deleted, to appear under "available columns" ### Observed Behavior custom field, that was previously deleted, appears under "available columns".
adam closed this issue 2025-12-29 19:27:26 +01:00
adam commented 2025-12-29 19:27:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 20, 2021):

I'm afraid we are no longer accepting bug reports for v2.11 or earlier releases. Please upgrade to v3.0.

@jeremystretch commented on GitHub (Sep 20, 2021): I'm afraid we are no longer accepting bug reports for v2.11 or earlier releases. Please upgrade to v3.0.
adam commented 2025-12-29 19:27:27 +01:00
Author
Owner
Copy Link

@opericgithub commented on GitHub (Sep 20, 2021):

initially I thought this was bug related to v2 only.
now i did some testing on v3, and can confirm the same behaviour.

@opericgithub commented on GitHub (Sep 20, 2021): initially I thought this was bug related to v2 only. now i did some testing on v3, and can confirm the same behaviour.
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#5394
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?