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 initial data from request.GET to script forms #3126

New Issue
Closed
opened 2025-12-29 18:25:57 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:25:57 +01:00
Owner
Copy Link

Originally created by @steffann on GitHub (Jan 6, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.7
  • NetBox version: 2.6.11

Proposed Functionality

Most NetBox forms are passed initial=request.GET to the constructor so that the request can pass initial values to the form. The extra/scrips functionality doesn't do that. I propose to add it to make forms behaviour consistent.

Use Case

I have a script that requires the user to select a device. With initial=request.GET I would be able to create a custom link from the device page with URL /extras/scripts/example/demo/?router={{ obj.id }} so that a user can easily click from the device page to the script page with the correct device pre-selected.

Database Changes

None

External Dependencies

None

As usual I'll implement this myself once accepted.

Originally created by @steffann on GitHub (Jan 6, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.7 * NetBox version: 2.6.11 ### Proposed Functionality Most NetBox forms are passed `initial=request.GET` to the constructor so that the request can pass initial values to the form. The extra/scrips functionality doesn't do that. I propose to add it to make forms behaviour consistent. ### Use Case I have a script that requires the user to select a device. With `initial=request.GET` I would be able to create a custom link from the device page with URL `/extras/scripts/example/demo/?router={{ obj.id }}` so that a user can easily click from the device page to the script page with the correct device pre-selected. ### Database Changes None ### External Dependencies None As usual I'll implement this myself once accepted.
adam added the status: acceptedtype: feature labels 2025-12-29 18:25:57 +01:00
adam closed this issue 2025-12-29 18:25:57 +01:00
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#3126
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?