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

Active/Inactive for contacts #6338

New Issue
Closed
opened 2025-12-29 19:39:35 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:39:35 +01:00
Owner
Copy Link

Originally created by @ghost on GitHub (Apr 10, 2022).

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

Please add the ability to assign contacts to have a status. Initial options would include:
Active, Inactive
Possibly more if you have other ideas.

Use case

Let's say I have rep for a particular software. He is a sales engineer and his contact information is listed in netbox. Now this person moves to a different role within the company and would then become an inactive contact for us, but we may still want to keep his contact information in netbox to refer to should we ever need to reach them again in the future for something.

Database changes

No response

External dependencies

No response

Originally created by @ghost on GitHub (Apr 10, 2022). ### NetBox version v3.2.0 ### Feature type New functionality ### Proposed functionality Please add the ability to assign contacts to have a status. Initial options would include: Active, Inactive Possibly more if you have other ideas. ### Use case Let's say I have rep for a particular software. He is a sales engineer and his contact information is listed in netbox. Now this person moves to a different role within the company and would then become an inactive contact for us, but we may still want to keep his contact information in netbox to refer to should we ever need to reach them again in the future for something. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:39:35 +01:00
adam closed this issue 2025-12-29 19:39:35 +01:00
adam commented 2025-12-29 19:39:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 11, 2022):

In such a scenario, you can just remove any assignments for the contact while keeping the contact itself in the database.

@jeremystretch commented on GitHub (Apr 11, 2022): In such a scenario, you can just remove any assignments for the contact while keeping the contact itself in the database.
adam commented 2025-12-29 19:39:36 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 11, 2022):

If I remove assignments (EX: group) then I lose visibility into what company or contact group that contact is for. I end up with lots of rouge contacts with little context on what company they represent.
Allowing a contact to be set as 'inactive' for a group gives me the flexibility to keep all information for this contact grouped with other contacts that work at the same company, while letting me know they are no longer a useful person to reach out to immediately, but perhaps a call of last resort if my 'active' contacts aren't responsive.
Just a way to track a lifecycle of interactions with different people within an organization I suppose.

@ghost commented on GitHub (Apr 11, 2022): If I remove assignments (EX: group) then I lose visibility into what company or contact group that contact is for. I end up with lots of rouge contacts with little context on what company they represent. Allowing a contact to be set as 'inactive' for a group gives me the flexibility to keep all information for this contact grouped with other contacts that work at the same company, while letting me know they are no longer a useful person to reach out to immediately, but perhaps a call of last resort if my 'active' contacts aren't responsive. Just a way to track a lifecycle of interactions with different people within an organization I suppose.
adam commented 2025-12-29 19:39:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 12, 2022):

It occurs to me that we already have an "inactive" priority available to the contact assignment, which should serve your use case quite well.

@jeremystretch commented on GitHub (Apr 12, 2022): It occurs to me that we already have an "inactive" priority available to the contact assignment, which should serve your use case quite well.
adam commented 2025-12-29 19:39:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 27, 2022):

Going to close this out as a solution has been identified and there's been no further discussion.

@jeremystretch commented on GitHub (Apr 27, 2022): Going to close this out as a solution has been identified and there's been no further discussion.
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#6338
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?