Enable specifying prefix scope object by name during bulk import #10559

Closed
opened 2025-12-29 21:33:07 +01:00 by adam · 2 comments
Owner

Originally created by @jeremystretch on GitHub (Dec 10, 2024).

NetBox version

v4.2-beta1

Feature type

New functionality

Triage priority

N/A

Proposed functionality

When bulk importing prefixes, enable the user to identify the scope object (region, site, etc.) by its name. Currently, the scope object must be specified by its numeric ID.

Use case

This approach is more user-friendly, as users typically refer to objects by name rather than by ID.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Dec 10, 2024). ### NetBox version v4.2-beta1 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality When bulk importing prefixes, enable the user to identify the scope object (region, site, etc.) by its name. Currently, the scope object must be specified by its numeric ID. ### Use case This approach is more user-friendly, as users typically refer to objects by name rather than by ID. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 21:33:07 +01:00
adam closed this issue 2025-12-29 21:33:07 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (May 8, 2025):

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 (May 8, 2025): 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/main/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jun 7, 2025):

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 (Jun 7, 2025): 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10559