starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Content type column should display model name only, omitting app name #7131

New Issue
Closed
opened 2025-12-29 20:19:32 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:19:32 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Oct 19, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.3.5

Feature type

Change to existing functionality

Proposed functionality

Table columns which indicate an object/content type should display only the model name, without its parent app. For example, when viewing a list of custom fields assigned to the site model, the "content types" column should display "Site" rather than "DCIM > site".

Use case

Omitting the app name for each type provides a cleaner view. While it's possible that plugins may introduce identical model names, this is unlikely to be problematic in practice, and viewing and this change is limited to lists of multiple objects. Viewing a single object would still display the associated app in additional to the model.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Oct 19, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.3.5 ### Feature type Change to existing functionality ### Proposed functionality Table columns which indicate an object/content type should display only the model name, without its parent app. For example, when viewing a list of custom fields assigned to the site model, the "content types" column should display "Site" rather than "DCIM > site". ### Use case Omitting the app name for each type provides a cleaner view. While it's possible that plugins may introduce identical model names, this is unlikely to be problematic in practice, and viewing and this change is limited to lists of multiple objects. Viewing a single object would still display the associated app in additional to the model. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:19:32 +01:00
adam closed this issue 2025-12-29 20:19:32 +01:00
adam commented 2025-12-29 20:19:34 +01:00
Author
Owner
Copy Link

@jcralbino commented on GitHub (Oct 19, 2022):

I think the users creating customs fields should be already aware of the model structure of netbox.

As a user I have accustomed to its view.

As a newbie developer i believe there is a strong possibility of collisions for the plug-in owner to create similar names to others already existing in netbox.
Can you force plug-in datamodel to appear with their "Pluginname > object ", while removing the primary only for netbox core models

@jcralbino commented on GitHub (Oct 19, 2022): I think the users creating customs fields should be already aware of the model structure of netbox. As a user I have accustomed to its view. As a newbie developer i believe there is a strong possibility of collisions for the plug-in owner to create similar names to others already existing in netbox. Can you force plug-in datamodel to appear with their "Pluginname > object ", while removing the primary only for netbox core models
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: feature
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#7131
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?