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

Way To Hide Blank/Empty Cards In UI When Not Used #9826

New Issue
Closed
opened 2025-12-29 21:23:16 +01:00 by adam · 7 comments
adam commented 2025-12-29 21:23:16 +01:00
Owner
Copy Link

Originally created by @mr1716 on GitHub (Jun 11, 2024).

NetBox version

v4.0.5

Feature type

New functionality

Proposed functionality

Currently in the Netbox UI, when there are cards that are not found or assigned such as shown in the screenshot below, it only makes the UI more crowded. It would be nice to have some way (unsure how it would be implemented) to provide users with a way to hide or show those cards.
Netbox Blank Cards

Use case

In instances where there are multiple blank cards, such as Public Netbox Interfaces Example, the page is significantly longer and harder to understand/read/use than it would and needs to be if these blank cards are not there. It would save time and make the tool easier to view.

Database changes

No response

External dependencies

No response

Originally created by @mr1716 on GitHub (Jun 11, 2024). ### NetBox version v4.0.5 ### Feature type New functionality ### Proposed functionality Currently in the Netbox UI, when there are cards that are not found or assigned such as shown in the screenshot below, it only makes the UI more crowded. It would be nice to have some way (unsure how it would be implemented) to provide users with a way to hide or show those cards. ![Netbox Blank Cards](https://github.com/netbox-community/netbox/assets/9115680/60d87257-0bc8-40a2-8f53-e631555b7d3d) ### Use case In instances where there are multiple blank cards, such as [Public Netbox Interfaces Example](https://demo.netbox.dev/dcim/interfaces/1723/), the page is significantly longer and harder to understand/read/use than it would and needs to be if these blank cards are not there. It would save time and make the tool easier to view. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:23:16 +01:00
adam closed this issue 2025-12-29 21:23:16 +01:00
adam commented 2025-12-29 21:23:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 11, 2024):

These cards are still shown because conveying that there are no such associated objects is still necessary information. For example, if we were to hide the tags panel when there are no tags assigned, users would likely become confused, unable to determine where to find tags for the object. We avoid this confusion by always presenting such information in a consistent manner.

@jeremystretch commented on GitHub (Jun 11, 2024): These cards are still shown because conveying that there are no such associated objects is still necessary information. For example, if we were to hide the tags panel when there are no tags assigned, users would likely become confused, unable to determine where to find tags for the object. We avoid this confusion by always presenting such information in a consistent manner.
adam commented 2025-12-29 21:23:17 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Jun 11, 2024):

That makes sense. So does that mean that the system always shows cards like Custom Fields as well even if there are no custom fields? To keep the same consistency?

@mr1716 commented on GitHub (Jun 11, 2024): That makes sense. So does that mean that the system always shows cards like Custom Fields as well even if there are no custom fields? To keep the same consistency?
adam commented 2025-12-29 21:23:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 11, 2024):

Yes, any custom fields which have been defined are always displayed.

@jeremystretch commented on GitHub (Jun 11, 2024): Yes, any custom fields which have been defined are always displayed.
adam commented 2025-12-29 21:23:18 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Jun 11, 2024):

Yes, any custom fields which have been defined are always displayed.

So when custom fields are NOT defined, does that mean that the Custom Fields card does NOT show up?

@mr1716 commented on GitHub (Jun 11, 2024): > Yes, any custom fields which have been defined are always displayed. So when custom fields are NOT defined, does that mean that the Custom Fields card does NOT show up?
adam commented 2025-12-29 21:23:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 11, 2024):

Bud you obviously can test this out yourself. I've explained why the proposed changes aren't going to be made. If you would prefer them, you're free to fork the project and make the changes yourself.

@jeremystretch commented on GitHub (Jun 11, 2024): Bud you obviously can test this out yourself. I've explained why the proposed changes aren't going to be made. If you would prefer them, you're free to fork the project and make the changes yourself.
adam commented 2025-12-29 21:23:19 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Jun 11, 2024):

@jeremystretch i understand that. But I’m letting you know that basing your decision on “this would likely confuse the users” but not have consistency in other areas, it really hurts the usability of the tool. And it looks like a design decision rather than one that’s actually been based on the user experience.

And I brought this up because as a user, I found this inconsistency weird and frustrating, with the intent of bringing it up to improve the tool. Maybe others have noticed this or not, but thought since it’s an open source tool, I might try to mention it in the event that others want this fixed as well.

@mr1716 commented on GitHub (Jun 11, 2024): @jeremystretch i understand that. But I’m letting you know that basing your decision on “this would likely confuse the users” but not have consistency in other areas, it really hurts the usability of the tool. And it looks like a design decision rather than one that’s actually been based on the user experience. And I brought this up because as a user, I found this inconsistency weird and frustrating, with the intent of bringing it up to improve the tool. Maybe others have noticed this or not, but thought since it’s an open source tool, I might try to mention it in the event that others want this fixed as well.
adam commented 2025-12-29 21:23:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 11, 2024):

And it looks like a design decision rather than one that’s actually been based on the user experience.

No, it's based on eight years of experience as both a user and a maintainer, and upon interactions with thousands of other users, rather than subjective opinion.

Locking as this has been rejected.

@jeremystretch commented on GitHub (Jun 11, 2024): > And it looks like a design decision rather than one that’s actually been based on the user experience. No, it's based on eight years of experience as both a user and a maintainer, and upon interactions with thousands of other users, rather than subjective opinion. Locking as this has been rejected.
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 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#9826
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?