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

Option to clone/inherit contact from Region/Location to locations/racks/devices #8291

New Issue
Closed
opened 2025-12-29 20:34:50 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:34:50 +01:00
Owner
Copy Link

Originally created by @deku-m on GitHub (Jul 5, 2023).

NetBox version

v3.5.4

Feature type

New functionality

Proposed functionality

When adding contacts, you need to add a contact to every locations/racks/devices.

If we can have some sort of inherit question option to also add the contact to the location and rack, this would save time. This could be a bulk/clone form or just asking do you also want to copy to your location/racks.

For example:
I add a contact to a region who is responsable for that, but they also have multiple locations under them.
You then need to add the same contact one by one on every location/rack and maybe even devices.
While i mostly see and think that someone is responsible for the location/region and also the racks.
When you add the contact now to a site you wont find it on the location or rack. But i would like to see this a

I understand that devices can have different contacts or someone different who is responsible.
But main case is to minimize the adding of contact to underlaying hierachy and inheritet or clone.
Its almost the same as bulk adding functionality or maybe provide a bulk import at contact assignment.

Use case

Providing a inherit function when adding a contact to a site with the automatically understanding that you also need it for a location or rack will save time adding the same contact to every underlaying location and rack under the site. Mostly you have a floormanager who is responsible for that site or location with the racks he has. There are also cases in datacenters that you have different contacts for different racks or locations. But providing a inherit button or question or even a attach to location/racks will save time to not add it to every single location and rack under the responsible person of that site

Database changes

Dont know exactly what.

External dependencies

N/A

Originally created by @deku-m on GitHub (Jul 5, 2023). ### NetBox version v3.5.4 ### Feature type New functionality ### Proposed functionality When adding contacts, you need to add a contact to every locations/racks/devices. If we can have some sort of inherit question option to also add the contact to the location and rack, this would save time. This could be a bulk/clone form or just asking do you also want to copy to your location/racks. **For example:** I add a contact to a region who is responsable for that, but they also have multiple locations under them. You then need to add the same contact one by one on every location/rack and maybe even devices. While i mostly see and think that someone is responsible for the location/region and also the racks. When you add the contact now to a site you wont find it on the location or rack. But i would like to see this a I understand that devices can have different contacts or someone different who is responsible. But main case is to minimize the adding of contact to underlaying hierachy and inheritet or clone. Its almost the same as bulk adding functionality or maybe provide a bulk import at contact assignment. ### Use case Providing a inherit function when adding a contact to a site with the automatically understanding that you also need it for a location or rack will save time adding the same contact to every underlaying location and rack under the site. Mostly you have a floormanager who is responsible for that site or location with the racks he has. There are also cases in datacenters that you have different contacts for different racks or locations. But providing a inherit button or question or even a attach to location/racks will save time to not add it to every single location and rack under the responsible person of that site ### Database changes Dont know exactly what. ### External dependencies N/A
adam added the type: featurepending closure labels 2025-12-29 20:34:50 +01:00
adam closed this issue 2025-12-29 20:34:50 +01:00
adam commented 2025-12-29 20:34:51 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 5, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please either modify your original proposal or start a GitHub discussion to discuss the proposed feature.

@jsenecal commented on GitHub (Jul 5, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please either modify your original proposal or start a GitHub discussion to discuss the proposed feature.
adam commented 2025-12-29 20:34:51 +01:00
Author
Owner
Copy Link

@deku-m commented on GitHub (Jul 6, 2023):

Updated case.

@deku-m commented on GitHub (Jul 6, 2023): Updated case.
adam commented 2025-12-29 20:34:52 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 11, 2023):

Bulk import of contact assignment is already an accepted issue https://github.com/netbox-community/netbox/issues/11307.

@abhi1693 commented on GitHub (Jul 11, 2023): Bulk import of contact assignment is already an accepted issue https://github.com/netbox-community/netbox/issues/11307.
adam commented 2025-12-29 20:34:52 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 10, 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 (Oct 10, 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:34:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 9, 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 (Nov 9, 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.
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 pending closure 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#8291
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?