starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-14 06:13:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Tags - Tagged Objects - Configure Table missing #10881

New Issue
Closed
opened 2025-12-29 21:37:11 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:37:11 +01:00
Owner
Copy Link

Originally created by @the-seppel on GitHub (Mar 12, 2025).

NetBox version

v.4.2.5

Feature type

New functionality

Proposed functionality

If you view all objects with a certain tag you can't configure the table view. e.g. custom fileds, location, rack, tenant

Use case

you can filter the tags for your purposes. e.g. you need a list with all objects in a tenant or location. At the moment you can only see ALL objects with a certain tag.

Database changes

I think there is no need for a db change because all information already exist. It's the view which must be extended to filter it.

External dependencies

Originally created by @the-seppel on GitHub (Mar 12, 2025). ### NetBox version v.4.2.5 ### Feature type New functionality ### Proposed functionality If you view all objects with a certain tag you can't configure the table view. e.g. custom fileds, location, rack, tenant ### Use case you can filter the tags for your purposes. e.g. you need a list with all objects in a tenant or location. At the moment you can only see ALL objects with a certain tag. ### Database changes I think there is no need for a db change because all information already exist. It's the view which must be extended to filter it. ### External dependencies -
adam added the type: feature label 2025-12-29 21:37:11 +01:00
adam closed this issue 2025-12-29 21:37:11 +01:00
adam commented 2025-12-29 21:37:12 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Mar 20, 2025):

This doesn't seem supportable -- the table of tagged objects is heterogeneous and the configuration of the table wouldn't apply uniformly to all the contents.

@bctiemann commented on GitHub (Mar 20, 2025): This doesn't seem supportable -- the table of tagged objects is heterogeneous and the configuration of the table wouldn't apply uniformly to all the contents.
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#10881
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?