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

Expand usage of contact and portal details #118

New Issue
Closed
opened 2025-12-29 15:33:53 +01:00 by adam · 4 comments
adam commented 2025-12-29 15:33:53 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Jul 1, 2016).

Expand the ability to apply contacts and portal details from carriers to manufacturers, racks, rack groups, and sites.

Originally created by @ryanmerolle on GitHub (Jul 1, 2016). Expand the ability to apply contacts and portal details from carriers to manufacturers, racks, rack groups, and sites.
adam closed this issue 2025-12-29 15:33:53 +01:00
adam commented 2025-12-29 15:33:54 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 7, 2016):

Could we also see phone, fax and perhaps basic contacts info for:

-noc
-support
-sales

(originally requested for sites)

@bellwood commented on GitHub (Jul 7, 2016): Could we also see phone, fax and perhaps basic contacts info for: -noc -support -sales (originally requested for sites)
adam commented 2025-12-29 15:33:54 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jul 7, 2016):

It sounds like allowing for contact type/relationship under the company or site would be useful.

Is fax number really that important for a contact!? Even with contracts or service orders, most of my vendors interact over email and do not provide fax details.

@ryanmerolle commented on GitHub (Jul 7, 2016): It sounds like allowing for contact type/relationship under the company or site would be useful. Is fax number really that important for a contact!? Even with contracts or service orders, most of my vendors interact over email and do not provide fax details.
adam commented 2025-12-29 15:33:55 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 7, 2016):

We fax subpoenas for abuse

@bellwood commented on GitHub (Jul 7, 2016): We fax subpoenas for abuse
adam commented 2025-12-29 15:33:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 4, 2017):

Additional contact details were added for sites in #756. I think that's sufficient for NetBox's role. Users also have the option now of adding custom fields to store any additional contact information they desire.

@jeremystretch commented on GitHub (Jan 4, 2017): Additional contact details were added for sites in #756. I think that's sufficient for NetBox's role. Users also have the option now of adding custom fields to store any additional contact information they desire.
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
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#118
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?