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

Custom Fields Groups #3577

New Issue
Closed
opened 2025-12-29 18:29:58 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:29:58 +01:00
Owner
Copy Link

Originally created by @lmgonzalezl on GitHub (Apr 16, 2020).

Environment

  • Python version: Python 3.6.8
  • NetBox version: v2.8.0

Proposed Functionality

Sometimes it is convenient to group the custom fields, for example in our case we use the object circuits to register macrolan circuits, RTB telephone lines, FTTH services, etc. Each one of these services requires specific customs fields and it would be interesting to be able to group them in some way in the view.

Use Case

An example of the utility previous would be to show groups of custom fields as follows

Custom Fields

Group VoIP
Custom Field 1
Custom Field 2
...
Group Macrolan
Custom Field 1
Custom Field 2
...

The groups may or may not be associated with the type of circuit, in this way only the specific custom fields for that group would be shown.

Database Changes

Yes, but I don't know how to describe it.

External Dependencies

Its no is necesary.

Originally created by @lmgonzalezl on GitHub (Apr 16, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: Python 3.6.8 <!-- Example: 3.6.9 --> * NetBox version: v2.8.0 <!-- Example: 2.7.3 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Sometimes it is convenient to group the custom fields, for example in our case we use the object circuits to register macrolan circuits, RTB telephone lines, FTTH services, etc. Each one of these services requires specific customs fields and it would be interesting to be able to group them in some way in the view. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case An example of the utility previous would be to show groups of custom fields as follows **Custom Fields** ------------------- **Group VoIP** Custom Field 1 Custom Field 2 ... **Group Macrolan** Custom Field 1 Custom Field 2 ... The groups may or may not be associated with the type of circuit, in this way only the specific custom fields for that group would be shown. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Yes, but I don't know how to describe it. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies Its no is necesary.
adam closed this issue 2025-12-29 18:29:59 +01:00
adam commented 2025-12-29 18:29:59 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Apr 19, 2020):

Thank you for submitting your idea. We are not currently extending custom fields to other models. Please see the FAQ for more detail.

@kobayashi commented on GitHub (Apr 19, 2020): Thank you for submitting your idea. We are not currently extending custom fields to other models. Please see the [FAQ](https://github.com/netbox-community/netbox/wiki/Frequently-Asked-Questions#can-we-add-custom-fields-to-more-models) for more detail.
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#3577
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?