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 request context to Reports #7575

New Issue
Closed
opened 2025-12-29 20:25:36 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:25:36 +01:00
Owner
Copy Link

Originally created by @abhi1693 on GitHub (Jan 27, 2023).

NetBox version

v3.4.3

Feature type

Change to existing functionality

Proposed functionality

I'm not sure at the implementation but similar to Scripts implementation. More discussion can be found at: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1674851789623179

Use case

I want to create reports which also sends the data to external tools. From such tools, I want the user's to be able to click on the objects in the message and return back to NetBox. Currently, this is not possible to do as the base URL is not accessible.

As bonus, I'd like to have the following implementations as well:

  • Request User
  • When a job is scheduled, the request context is still available in automated runs

Database changes

No response

External dependencies

No response

Originally created by @abhi1693 on GitHub (Jan 27, 2023). ### NetBox version v3.4.3 ### Feature type Change to existing functionality ### Proposed functionality I'm not sure at the implementation but similar to Scripts implementation. More discussion can be found at: https://netdev-community.slack.com/archives/C01P0FRSXRV/p1674851789623179 ### Use case I want to create reports which also sends the data to external tools. From such tools, I want the user's to be able to click on the objects in the message and return back to NetBox. Currently, this is not possible to do as the base URL is not accessible. As bonus, I'd like to have the following implementations as well: - Request User - When a job is scheduled, the request context is still available in automated runs ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:25:36 +01:00
adam closed this issue 2025-12-29 20:25:36 +01:00
adam commented 2025-12-29 20:25:37 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jan 27, 2023):

Please expand on the proposed functionality as the slack link may not be available down the road. But otherwise I think the general consensus based on that conversation was that this would be a good thing :)

@jsenecal commented on GitHub (Jan 27, 2023): Please expand on the _proposed functionality_ as the slack link may not be available down the road. But otherwise I think the general consensus based on that conversation was that this would be a good thing :)
adam commented 2025-12-29 20:25:37 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Apr 7, 2023):

@jeremystretch Could this be taken up for 3.5 release within the new reports functionality?

@abhi1693 commented on GitHub (Apr 7, 2023): @jeremystretch Could this be taken up for 3.5 release within the new reports functionality?
adam commented 2025-12-29 20:25:37 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (May 5, 2023):

Since this hasn't had much traction, we may not need this due to deprecation in https://github.com/netbox-community/netbox/issues/12510

@abhi1693 commented on GitHub (May 5, 2023): Since this hasn't had much traction, we may not need this due to deprecation in https://github.com/netbox-community/netbox/issues/12510
adam commented 2025-12-29 20:25:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 25, 2023):

Agreed; I'm going to punt on this.

@jeremystretch commented on GitHub (May 25, 2023): Agreed; I'm going to punt on this.
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#7575
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?