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

Custom fields panel absent from object view in UI #1894

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

Originally created by @xonacs on GitHub (Aug 6, 2018).

Environment

  • Python version: 3.4.5
  • NetBox version: 2.4

Steps to Reproduce

Login to Netbox and click on an object, tenant etc. that has a custom field attached to it.

For example, I have 10 custom fields on Tenants. If I edit a tenant I can see all custom fields. I can search by custom field. But when I click the tenant name, I don't see the values of these custom fields.

Expected Behavior

Up until the previous version, all values from custom fields used to show up.

Observed Behavior

All custom values do not show up in view mode. Only in edit mode.

Originally created by @xonacs on GitHub (Aug 6, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.4.5 * NetBox version: 2.4 <!-- Describe in detail the steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). --> ### Steps to Reproduce Login to Netbox and click on an object, tenant etc. that has a custom field attached to it. For example, I have 10 custom fields on Tenants. If I edit a tenant I can see all custom fields. I can search by custom field. But when I click the tenant name, I don't see the values of these custom fields. <!-- What did you expect to happen? --> ### Expected Behavior Up until the previous version, all values from custom fields used to show up. <!-- What happened instead? --> ### Observed Behavior All custom values do not show up in view mode. Only in edit mode.
adam added the type: bugstatus: accepted labels 2025-12-29 17:20:10 +01:00
adam closed this issue 2025-12-29 17:20:11 +01:00
adam commented 2025-12-29 17:20:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 6, 2018):

Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided here. This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!

@jeremystretch commented on GitHub (Aug 6, 2018): Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided [here](https://github.com/digitalocean/netbox/tree/develop/.github/ISSUE_TEMPLATE). This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!
adam commented 2025-12-29 17:20:12 +01:00
Author
Owner
Copy Link

@xonacs commented on GitHub (Aug 6, 2018):

Updated

@xonacs commented on GitHub (Aug 6, 2018): Updated
adam commented 2025-12-29 17:20:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 6, 2018):

This has been resolved in the develop branch. Leaving it open for reference temporarily so people (hopefully) don't open duplicate issues.

@jeremystretch commented on GitHub (Aug 6, 2018): This has been resolved in the `develop` branch. Leaving it open for reference temporarily so people (hopefully) don't open duplicate issues.
adam commented 2025-12-29 17:20:12 +01:00
Author
Owner
Copy Link

@xonacs commented on GitHub (Aug 6, 2018):

fix worked for me, thanks!

@xonacs commented on GitHub (Aug 6, 2018): fix worked for me, thanks!
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#1894
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?