Arrange the device type & module type fields of component template model forms behind tabs #10163

Closed
opened 2025-12-29 21:27:42 +01:00 by adam · 1 comment
Owner

Originally created by @jeremystretch on GitHub (Aug 30, 2024).

Originally assigned to: @jnovinger on GitHub.

NetBox version

v4.1-beta1

Feature type

Change to existing functionality

Proposed functionality

Currently, when creating or editing any kind of device component template, both the device_type and module_type fields are displayed:

screenshot

These fields should be grouped into tabs (using TabbedGroups), such that only one field can be displayed at any time.

Use case

These fields are mutually exclusive, and showing both may be confusing to the user.

Database changes

None

External dependencies

None

Originally created by @jeremystretch on GitHub (Aug 30, 2024). Originally assigned to: @jnovinger on GitHub. ### NetBox version v4.1-beta1 ### Feature type Change to existing functionality ### Proposed functionality Currently, when creating or editing any kind of device component template, both the `device_type` and `module_type` fields are displayed: ![screenshot](https://github.com/user-attachments/assets/685fb30d-7c71-4542-8cc9-6c4f41880f83) These fields should be grouped into tabs (using `TabbedGroups`), such that only one field can be displayed at any time. ### Use case These fields are mutually exclusive, and showing both may be confusing to the user. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:27:42 +01:00
adam closed this issue 2025-12-29 21:27:42 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Apr 25, 2025):

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 (Apr 25, 2025): 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/main/CONTRIBUTING.md).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10163