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

Add status attribute in the search results for devices #8950

New Issue
Closed
opened 2025-12-29 20:43:15 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:43:15 +01:00
Owner
Copy Link

Originally created by @markkuleinio on GitHub (Dec 12, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

V3.7-beta1

Feature type

Change to existing functionality

Proposed functionality

Currently (in the new search result list of v3.7-beta1) the following fields/attributes are shown for devices that are shown in search results:

'site', 'location', 'rack', 'device_type', 'role', 'tenant', 'platform', 'serial', 'asset_tag', 'description',

I propose adding status field there as well, preferably somewhere near the beginning of the list.

Use case

When search results are shown it is important to see which devices (if any) are active and which are decommissioning etc.

Database changes

None

External dependencies

None (as far as I understand)

Originally created by @markkuleinio on GitHub (Dec 12, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version V3.7-beta1 ### Feature type Change to existing functionality ### Proposed functionality Currently (in the new search result list of v3.7-beta1) the following fields/attributes are shown for devices that are shown in search results: 'site', 'location', 'rack', 'device_type', 'role', 'tenant', 'platform', 'serial', 'asset_tag', 'description', I propose adding status field there as well, preferably somewhere near the beginning of the list. ### Use case When search results are shown it is important to see which devices (if any) are active and which are decommissioning etc. ### Database changes None ### External dependencies None (as far as I understand)
adam added the status: acceptedtype: featurebeta labels 2025-12-29 20:43:15 +01:00
adam closed this issue 2025-12-29 20:43:15 +01:00
adam commented 2025-12-29 20:43:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 12, 2023):

It's probably worth doing a full audit across all models to identify any other fields that were omitted in error.

@jeremystretch commented on GitHub (Dec 12, 2023): It's probably worth doing a full audit across all models to identify any other fields that were omitted in error.
adam commented 2025-12-29 20:43:17 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Dec 13, 2023):

Would it be possible to make these lists configurable, maybe like we can do for choice sets today? For example, I can think of scenarios within our deployment where it would be nice to include particular custom fields in the display attributes on search results.

@sleepinggenius2 commented on GitHub (Dec 13, 2023): Would it be possible to make these lists configurable, maybe like we can do for choice sets today? For example, I can think of scenarios within our deployment where it would be nice to include particular custom fields in the display attributes on search results.
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 beta 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#8950
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?