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

Allow filtering of ObjectVar and MultiObjectVar input selections for scripts #10444

New Issue
Closed
opened 2025-12-29 21:31:32 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:31:32 +01:00
Owner
Copy Link

Originally created by @atownson on GitHub (Nov 6, 2024).

Originally assigned to: @atownson on GitHub.

NetBox version

v4.1.6

Feature type

New functionality

Triage priority

N/A

Proposed functionality

Proposing to extend the functionality of the object selection inputs (ObjectVar and MultiObjectVar) in scripts to be able to filter the selection in the same fashion that's available in the create/edit forms.
image
I might suggest adding the optional parameters selector (boolean with a default of False) and query_params (dictionary) to both ObjectVar and MultiObjectVar classes so that it matches the form parameters. selector=True would show the filter button, and the query_params dictionary to be used to apply the initial filtering.

Use case

Our NetBox instance relies on a few scripts to assist in creating items. Currently we use separate inputs to control filtering (similar to the old behavior of NetBox). Adding the optional filtering would improve the user experience in the same way filtering improved the user experience when using the create/edit forms.

Database changes

None

External dependencies

None

Originally created by @atownson on GitHub (Nov 6, 2024). Originally assigned to: @atownson on GitHub. ### NetBox version v4.1.6 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality Proposing to extend the functionality of the object selection inputs (ObjectVar and MultiObjectVar) in scripts to be able to filter the selection in the same fashion that's available in the create/edit forms. ![image](https://github.com/user-attachments/assets/ba316604-ab96-47c3-b1b0-3502cd2635e5) I might suggest adding the optional parameters `selector` (boolean with a default of False) and `query_params` (dictionary) to both ObjectVar and MultiObjectVar classes so that it matches the form parameters. `selector=True` would show the filter button, and the `query_params` dictionary to be used to apply the initial filtering. ### Use case Our NetBox instance relies on a few scripts to assist in creating items. Currently we use separate inputs to control filtering (similar to the old behavior of NetBox). Adding the optional filtering would improve the user experience in the same way filtering improved the user experience when using the create/edit forms. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:31:32 +01:00
adam closed this issue 2025-12-29 21:31:32 +01:00
adam commented 2025-12-29 21:31:33 +01:00
Author
Owner
Copy Link

@atownson commented on GitHub (Feb 6, 2025):

I can work on this.

@atownson commented on GitHub (Feb 6, 2025): I can work on this.
adam commented 2025-12-29 21:31:33 +01:00
Author
Owner
Copy Link

@atownson commented on GitHub (Feb 24, 2025):

Could this be assigned to me, please?

@atownson commented on GitHub (Feb 24, 2025): Could this be assigned to me, please?
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 complexity: low 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#10444
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?