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

Document supported child objects on bulk import views #7365

New Issue
Open
opened 2025-12-29 20:22:20 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:22:20 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Dec 15, 2022).

NetBox version

v3.4.0

Feature type

Change to existing functionality

Proposed functionality

Certain types of objects in NetBox, such as device types and module types, support the simultaneous import of various child objects (e.g. component templates) during bulk import. However, these child objects are not documented as supported under each form as they local fields ares. Ideally, we should annotate support for child objects wherever relevant.

Use case

This will convey to users that the functionality exists where they might not otherwise realize, and serve as a reference.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Dec 15, 2022). ### NetBox version v3.4.0 ### Feature type Change to existing functionality ### Proposed functionality Certain types of objects in NetBox, such as device types and module types, support the simultaneous import of various child objects (e.g. component templates) during bulk import. However, these child objects are not documented as supported under each form as they local fields ares. Ideally, we should annotate support for child objects wherever relevant. ### Use case This will convey to users that the functionality exists where they might not otherwise realize, and serve as a reference. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetboxstatus: backlogcomplexity: low labels 2025-12-29 20:22:20 +01:00
adam commented 2025-12-29 20:22:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 14, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Feb 14, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:22:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 17, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Mar 17, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
adam commented 2025-12-29 20:22:23 +01:00
Author
Owner
Copy Link

@vyas-n commented on GitHub (May 19, 2023):

Hi @jeremystretch I'd like to volunteer for documenting this behaviour.

Anything I need to communicate beforehand, or should I start with a PR?

@vyas-n commented on GitHub (May 19, 2023): Hi @jeremystretch I'd like to volunteer for documenting this behaviour. Anything I need to communicate beforehand, or should I start with a PR?
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 complexity: low netbox status: backlog 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#7365
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?