-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document supported child objects on bulk import views #11204
Comments
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. |
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. |
Hi @jeremystretch I'd like to volunteer for documenting this behaviour. Anything I need to communicate beforehand, or should I start with a PR? |
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
The text was updated successfully, but these errors were encountered: