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

Manufacturer Information #1177

New Issue
Closed
opened 2025-12-29 16:29:46 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:29:46 +01:00
Owner
Copy Link

Originally created by @kopacko on GitHub (Aug 17, 2017).

Issue type: feature request

Python version:
NetBox version:

Would it be possible to get some fields created for the manufacturer page?

Support information (account number/support portal/etc)

Also the ability to create custom fields for the manufacturer page would be very nice as well.

Originally created by @kopacko on GitHub (Aug 17, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: feature request <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** **NetBox version:** <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> Would it be possible to get some fields created for the manufacturer page? Support information (account number/support portal/etc) Also the ability to create custom fields for the manufacturer page would be very nice as well.
adam added the status: duplicate label 2025-12-29 16:29:46 +01:00
adam closed this issue 2025-12-29 16:29:46 +01:00
adam commented 2025-12-29 16:29:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 17, 2017):

This feature request lacks sufficient detail to be actionable. Per the contributing guidelines:

When submitting a feature request on GitHub, be sure to include the following:

  • A detailed description of the proposed functionality
  • A use case for the feature; who would use it and what value it would add to NetBox
  • A rough description of changes necessary to the database schema (if applicable)
  • Any third-party libraries or other resources which would be involved

Please extend the request so that it meets all of these requirements. If no response is received within a week, this issue will be closed.

@jeremystretch commented on GitHub (Aug 17, 2017): This feature request lacks sufficient detail to be actionable. Per the [contributing guidelines](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md): > When submitting a feature request on GitHub, be sure to include the following: > > * A detailed description of the proposed functionality > * A use case for the feature; who would use it and what value it would add to NetBox > * A rough description of changes necessary to the database schema (if applicable) > * Any third-party libraries or other resources which would be involved Please extend the request so that it meets all of these requirements. If no response is received within a week, this issue will be closed.
adam commented 2025-12-29 16:29:46 +01:00
Author
Owner
Copy Link

@kopacko commented on GitHub (Aug 17, 2017):

Adding some basic fields to the manufacturer page, like a spot for support information specific to that manufacturer, the URL to the vendor support site, specific company credentials for support access, etc. All similar things provided under the Providers page, for example.

When submitting a feature request on GitHub, be sure to include the following:

  • A detailed description of the proposed functionality

PROVIDER > SUPPORT INFO (Similar information for manufacturers)
--- Account number
--- Portal
--- Contact

  • A use case for the feature; who would use it and what value it would add to NetBox

USE CASE > Contacting Manufacturer Support (not needing to maintain a separate DB some place else with key support info.

  • A rough description of changes necessary to the database schema (if applicable)

NOT A CLUE

  • Any third-party libraries or other resources which would be involved

UNKNOWN (Don't think any third-party anything would be needed.)

Also, being able to add custom fields to any page. (I am not sure what else you need for that to be "actionable".)

Everything I have been mentioning/requested/etc has be summarily dismissed or blatantly no. These are all things that I am being asked of by my peers/bosses/etc or running into myself as we being using NetBox.

@kopacko commented on GitHub (Aug 17, 2017): Adding some basic fields to the manufacturer page, like a spot for support information specific to that manufacturer, the URL to the vendor support site, specific company credentials for support access, etc. All similar things provided under the Providers page, for example. **When submitting a feature request on GitHub, be sure to include the following:** - A detailed description of the proposed functionality PROVIDER > SUPPORT INFO (Similar information for manufacturers) --- Account number --- Portal --- Contact - A use case for the feature; who would use it and what value it would add to NetBox USE CASE > Contacting Manufacturer Support (not needing to maintain a separate DB some place else with key support info. - A rough description of changes necessary to the database schema (if applicable) NOT A CLUE - Any third-party libraries or other resources which would be involved UNKNOWN (Don't think any third-party anything would be needed.) Also, being able to add custom fields to any page. (I am not sure what else you need for that to be "actionable".) Everything I have been mentioning/requested/etc has be summarily dismissed or blatantly no. These are all things that I am being asked of by my peers/bosses/etc or running into myself as we being using NetBox.
adam commented 2025-12-29 16:29:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 17, 2017):

This sounds like a duplicate of #182. Please review that issue and add any additional comments there.

@jeremystretch commented on GitHub (Aug 17, 2017): This sounds like a duplicate of #182. Please review that issue and add any additional comments there.
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 status: duplicate
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#1177
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?