Unset optional custom integer fields are displayed as "None" instead of "—" #3530

Closed
opened 2025-12-29 18:29:42 +01:00 by adam · 0 comments
Owner

Originally created by @u1735067 on GitHub (Apr 2, 2020).

Environment

  • Python version: 3.7.7
  • NetBox version: 2.7.10

Steps to Reproduce

  1. Create an optional custom integer field
  2. Display an object having this custom field

Expected Behavior

Custom field displays "—" like for other unset fields

Observed Behavior

"None" is displayed

Note

I have a patch proposal @ https://github.com/netbox-community/netbox/compare/develop...Alex131089:patch-1

Originally created by @u1735067 on GitHub (Apr 2, 2020). ### Environment * Python version: 3.7.7 * NetBox version: 2.7.10 ### Steps to Reproduce 1. Create an optional custom integer field 2. Display an object having this custom field <!-- What did you expect to happen? --> ### Expected Behavior Custom field displays "—" like for other unset fields <!-- What happened instead? --> ### Observed Behavior "None" is displayed #### Note I have a patch proposal @ https://github.com/netbox-community/netbox/compare/develop...Alex131089:patch-1
adam added the type: bugstatus: accepted labels 2025-12-29 18:29:42 +01:00
adam closed this issue 2025-12-29 18:29:43 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3530