Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
jeremystretch opened this issue Aug 30, 2024 · 1 comment · Fixed by #19357
Closed

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

jeremystretch opened this issue Aug 30, 2024 · 1 comment · Fixed by #19357
Assignees
@jnovinger
Labels
complexity: low Requires minimal effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone
v4.2.9

Comments

@jeremystretch
Copy link
Member

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
@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation complexity: low Requires minimal effort to implement labels Aug 30, 2024
@jeremystretch jeremystretch added the netbox label Nov 1, 2024 — with Linear
@github-actions GitHub Actions
Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Apr 25, 2025
@jnovinger jnovinger self-assigned this Apr 28, 2025
@jnovinger jnovinger added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Apr 28, 2025
@jnovinger jnovinger mentioned this issue Apr 29, 2025
Merged
bctiemann added a commit that referenced this issue Apr 30, 2025
@bctiemann
Merge pull request #19357 from netbox-community/17319-device-and-modu…
fadc358 
…le-type-behind-tabs

Fixes #17319: Arrange device and module type fields behind tab in com…
@jeremystretch jeremystretch added this to the v4.2.9 milestone Apr 30, 2025
@jeremystretch jeremystretch mentioned this issue Apr 30, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jnovinger jnovinger

Labels
complexity: low Requires minimal effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
v4.2.9
Development

Successfully merging a pull request may close this issue.

Fixes #17319: Arrange device and module type fields behind tab in com… netbox-community/netbox
2 participants
@jnovinger @jeremystretch