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

Move non-racked devices to a separate tab under the rack view #7666

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

Originally created by @LHBL2003 on GitHub (Feb 22, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.4.5

Feature type

Change to existing functionality

Proposed functionality

Set the list "Non-Racked Devices" via the rack or as a separate tab/register

image

Maybe even with a signal colour so that you can recognise more quickly that there is a special feature here, which is not the case with every rack.
image

THX to @abhi1693 for the basic image.

Use case

I have been thinking about raising this point for months. But I realise again and again that it is important.

Racks with 42 units are so long that you can't see the "non-racked devices" area on a 24" monitor. That's why you don't pay attention to them. Either they are devices that are not sorted or devices that cannot be installed in a unit, e.g. socket outlets, small devices that are screwed to the rack, e.g. temperature monitors.

Translated with www.DeepL.com/Translator (free version)

Database changes

No response

External dependencies

No response

Originally created by @LHBL2003 on GitHub (Feb 22, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.4.5 ### Feature type Change to existing functionality ### Proposed functionality Set the list "Non-Racked Devices" via the rack or as a separate tab/register ![image](https://user-images.githubusercontent.com/46369917/221256776-a4529e4d-97b3-413b-86a9-79be97d26c1a.png) Maybe even with a signal colour so that you can recognise more quickly that there is a special feature here, which is not the case with every rack. ![image](https://user-images.githubusercontent.com/46369917/221257534-4fdc34c3-accb-4891-9e7a-1dd1f7c94cb5.png) THX to @abhi1693 for the basic image. ### Use case I have been thinking about raising this point for months. But I realise again and again that it is important. Racks with 42 units are so long that you can't see the "non-racked devices" area on a 24" monitor. That's why you don't pay attention to them. Either they are devices that are not sorted or devices that cannot be installed in a unit, e.g. socket outlets, small devices that are screwed to the rack, e.g. temperature monitors. Translated with www.DeepL.com/Translator (free version) ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:26:40 +01:00
adam closed this issue 2025-12-29 20:26:40 +01:00
adam commented 2025-12-29 20:26:40 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Feb 23, 2023):

I think non racked devices should simply be moved to a view tab. That way if they exist you see them at the top of the page with a count.

@abhi1693 commented on GitHub (Feb 23, 2023): I think non racked devices should simply be moved to a view tab. That way if they exist you see them at the top of the page with a count.
adam commented 2025-12-29 20:26:41 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Feb 23, 2023):

Do I understand that correctly, is that a counter-suggestion from you? Or does this function exist?

@LHBL2003 commented on GitHub (Feb 23, 2023): Do I understand that correctly, is that a counter-suggestion from you? Or does this function exist?
adam commented 2025-12-29 20:26:41 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Feb 23, 2023):

It's a counter suggestion and something once accepted can be implemented natively. I already have a patch that does exactly this in our netbox. It basically moves the list at the bottom to a tab at the top with a count

@abhi1693 commented on GitHub (Feb 23, 2023): It's a counter suggestion and something once accepted can be implemented natively. I already have a patch that does exactly this in our netbox. It basically moves the list at the bottom to a tab at the top with a count
adam commented 2025-12-29 20:26:41 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Feb 23, 2023):

@abhi1693 do you have an issue # for that feature request ?

@jsenecal commented on GitHub (Feb 23, 2023): @abhi1693 do you have an issue # for that feature request ?
adam commented 2025-12-29 20:26:41 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Feb 23, 2023):

@jsenecal I'm sorry but I don't follow you.

@abhi1693 commented on GitHub (Feb 23, 2023): @jsenecal I'm sorry but I don't follow you.
adam commented 2025-12-29 20:26:42 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Feb 23, 2023):

I already have a patch that does exactly this in our netbox. It basically moves the list at the bottom to a tab at the top with a count

@jsenecal commented on GitHub (Feb 23, 2023): > I already have a patch that does exactly this in our netbox. It basically moves the list at the bottom to a tab at the top with a count
adam commented 2025-12-29 20:26:42 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Feb 23, 2023):

Oh, I never opened an issue for this and directly applied the patch in my Netbox code. So, if the suggestion counter to adding the label is accepted, for this issue itself I'll raise the pr

Edit: Here is something to provide more context
image

@abhi1693 commented on GitHub (Feb 23, 2023): Oh, I never opened an issue for this and directly applied the patch in my Netbox code. So, if the suggestion counter to adding the label is accepted, for this issue itself I'll raise the pr Edit: Here is something to provide more context ![image](https://user-images.githubusercontent.com/5083532/221167922-08e7404e-bce0-40d8-a5e7-3fde66be9934.png)
adam commented 2025-12-29 20:26:42 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Feb 23, 2023):

@LHBL2003 If you are happy with what @abhi1693 suggested, please update your proposal to reflect this.

Thank you all,

@jsenecal commented on GitHub (Feb 23, 2023): @LHBL2003 If you are happy with what @abhi1693 suggested, please update your proposal to reflect this. Thank you all,
adam commented 2025-12-29 20:26:42 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Feb 24, 2023):

I think that's a great idea. Maybe you could make sure that the grey background is orange?
Then it would be more eye-catching that there is a special feature that is not present in every rack.

@LHBL2003 commented on GitHub (Feb 24, 2023): I think that's a great idea. Maybe you could make sure that the grey background is orange? Then it would be more eye-catching that there is a special feature that is not present in every rack.
adam commented 2025-12-29 20:26:43 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Feb 24, 2023):

I don't think color would change as that's netbox internal AFAIK. Also, such tabs are used throughout the UI, it should remain consistent as far as UI is considered. Rest as shown in my screenshot is applicable.

@abhi1693 commented on GitHub (Feb 24, 2023): I don't think color would change as that's netbox internal AFAIK. Also, such tabs are used throughout the UI, it should remain consistent as far as UI is considered. Rest as shown in my screenshot is applicable.
adam commented 2025-12-29 20:26:43 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Feb 24, 2023):

OK

@LHBL2003 commented on GitHub (Feb 24, 2023): OK
adam commented 2025-12-29 20:26:43 +01:00
Author
Owner
Copy Link

@LHBL2003 commented on GitHub (Feb 24, 2023):

@jsenecal: Then I would say @abhi1693 suggestion should go into the release function or?

@LHBL2003 commented on GitHub (Feb 24, 2023): @jsenecal: Then I would say @abhi1693 suggestion should go into the release function or?
adam commented 2025-12-29 20:26:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 4, 2023):

Is there a real benefit of establishing a tabbed view for these devices as opposed to just linking to the filtered devices list?

@jeremystretch commented on GitHub (May 4, 2023): Is there a real benefit of establishing a tabbed view for these devices as opposed to just linking to the filtered devices list?
adam commented 2025-12-29 20:26:44 +01:00
Author
Owner
Copy Link

@JoeIzzard commented on GitHub (May 10, 2023):

I'd rather it be a tab than a link to the Device list so I can easily change back. If it's a link to the device list then I wouldn't have an easy way to tab back to the rack view which I may be switching between several times.

@JoeIzzard commented on GitHub (May 10, 2023): I'd rather it be a tab than a link to the Device list so I can easily change back. If it's a link to the device list then I wouldn't have an easy way to tab back to the rack view which I may be switching between several times.
adam commented 2025-12-29 20:26:44 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 12, 2023):

Based on https://github.com/netbox-community/netbox/issues/11803#issuecomment-1442403948, @abhi1693, I think you already had a fix implemented for this, is that right ?

@jsenecal commented on GitHub (Jul 12, 2023): Based on https://github.com/netbox-community/netbox/issues/11803#issuecomment-1442403948, @abhi1693, I think you already had a fix implemented for this, is that right ?
adam commented 2025-12-29 20:26:44 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Jul 12, 2023):

@jsenecal I don't have any right now, but can submit later if we are accepting this

@abhi1693 commented on GitHub (Jul 12, 2023): @jsenecal I don't have any right now, but can submit later if we are accepting this
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: accepted type: feature
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#7666
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?