Minor UI/UX tweaks to menu structure #7120

Closed
opened 2025-12-29 20:19:27 +01:00 by adam · 2 comments
Owner

Originally created by @cpmills1975 on GitHub (Oct 19, 2022).

NetBox version

3.3.5

Feature type

Change to existing functionality

Proposed functionality

That Modules move from the Devices -> Devices menu to the Devices -> Components* menu.

The "Device Components" becomes simply "Components"

Use case

While modules are clearly more powerful than something like an Interface or a Power Port, they have to exist within a module bay on a device. I'd suggest therefore that they can only really be considered a component of the device within which they are instantiated.

Given both modules and devices can contain interfaces, console ports, etc; the term Device Components is not strictly true as they can also be called Module Components. I'd like to suggest therefore that the "Device Components" menu becomes simply "Components".

Database changes

None

External dependencies

None.

Originally created by @cpmills1975 on GitHub (Oct 19, 2022). ### NetBox version 3.3.5 ### Feature type Change to existing functionality ### Proposed functionality That Modules move from the Devices -> Devices menu to the Devices -> Components* menu. The "Device Components" becomes simply "Components" ### Use case While modules are clearly more powerful than something like an Interface or a Power Port, they have to exist within a module bay on a device. I'd suggest therefore that they can only really be considered a component of the device within which they are instantiated. Given both modules and devices can contain interfaces, console ports, etc; the term Device Components is not strictly true as they can also be called Module Components. I'd like to suggest therefore that the "Device Components" menu becomes simply "Components". ### Database changes None ### External dependencies None.
adam added the type: featurepending closure labels 2025-12-29 20:19:27 +01:00
adam closed this issue 2025-12-29 20:19:27 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 19, 2022):

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 (Dec 19, 2022): 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/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jan 18, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 18, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7120