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

Standardize the representation of content types across import & export functions #5678

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

Originally created by @jeremystretch on GitHub (Nov 17, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.10

Feature type

Change to existing functionality

Proposed functionality

Always represent "raw" values for content type references in their <app>.<model> format. For example, the custom fields import form expects content types to be identified in this format, however the export view shows a slightly more human-friendly format that is incompatible with the import form. This can be confusing for users.

Use case

Standardizing the representation of content types for both import and export makes the data more portable and easier to manipulate.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Nov 17, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.10 ### Feature type Change to existing functionality ### Proposed functionality Always represent "raw" values for content type references in their `<app>.<model>` format. For example, the custom fields import form expects content types to be identified in this format, however the export view shows a slightly more human-friendly format that is incompatible with the import form. This can be confusing for users. ### Use case Standardizing the representation of content types for both import and export makes the data more portable and easier to manipulate. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:31:23 +01:00
adam closed this issue 2025-12-29 19:31:23 +01:00
adam commented 2025-12-29 19:31:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 17, 2021):

This has been completed for the upcoming v3.1 release.

@jeremystretch commented on GitHub (Nov 17, 2021): This has been completed for the upcoming v3.1 release.
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#5678
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?