Ability to selectively hide custom fields from the web UI #1760

Closed
opened 2025-12-29 17:18:53 +01:00 by adam · 3 comments
Owner

Originally created by @pm17788 on GitHub (May 30, 2018).

Issue type

[x] Feature request

Environment

  • Python version: 3.5.4
  • NetBox version: 2.3.2

Feature Request:

As a thought, what about having a flag on a custom field which would hide it from the UI view? Still present via API, though.
I find that I have users who just want the WebUI, and for them, an overabundance of custom fields is confusing (especially those which are packed for machine-parseability). The API users I basically don't care about in that if they're using the API, it's on them to filter stuff they don't want to see .

Originally created by @pm17788 on GitHub (May 30, 2018). ### Issue type [x] Feature request ### Environment * Python version: 3.5.4 * NetBox version: 2.3.2 ### Feature Request: As a thought, what about having a flag on a custom field which would hide it from the UI view? Still present via API, though. I find that I have users who just want the WebUI, and for them, an overabundance of custom fields is confusing (especially those which are packed for machine-parseability). The API users I basically don't care about in that if they're using the API, it's on them to filter stuff they don't want to see .
adam closed this issue 2025-12-29 17:18:53 +01:00
Author
Owner

@pm17788 commented on GitHub (May 30, 2018):

A split-off from #2120

@pm17788 commented on GitHub (May 30, 2018): A split-off from #2120
Author
Owner

@a31amit commented on GitHub (Aug 23, 2018):

@jeremystretch https://github.com/digitalocean/netbox/issues/2383 seems a little different where the user can selectively display them on device page and see everything in inventory page.

If you consider that, this can be included altogether.

@a31amit commented on GitHub (Aug 23, 2018): @jeremystretch https://github.com/digitalocean/netbox/issues/2383 seems a little different where the user can selectively display them on device page and see everything in inventory page. If you consider that, this can be included altogether.
Author
Owner

@jeremystretch commented on GitHub (Jan 4, 2019):

I had previously marked this as accepted, but after giving it more thought I don't think it's a good fit. We try to maintain parity between the web UI and the API, and this would intentionally diverge from that. It's also worth pointing out that config contexts have been implemented since this was proposed, which may provide a better place to store data that isn't necessarily interesting to users.

@jeremystretch commented on GitHub (Jan 4, 2019): I had previously marked this as accepted, but after giving it more thought I don't think it's a good fit. We try to maintain parity between the web UI and the API, and this would intentionally diverge from that. It's also worth pointing out that config contexts have been implemented since this was proposed, which may provide a better place to store data that isn't necessarily interesting to users.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1760