Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add request context to Reports #11612

Closed
abhi1693 opened this issue Jan 27, 2023 · 4 comments
Closed

Add request context to Reports #11612

abhi1693 opened this issue Jan 27, 2023 · 4 comments
Labels
type: feature Introduction of new functionality to the application

Comments

@abhi1693
Copy link
Member

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

@abhi1693 abhi1693 added the type: feature Introduction of new functionality to the application label Jan 27, 2023
@jsenecal
Copy link
Contributor

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 jsenecal added the status: revisions needed This issue requires additional information to be actionable label Jan 27, 2023
@kkthxbye-code kkthxbye-code added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: revisions needed This issue requires additional information to be actionable labels Feb 17, 2023
@abhi1693
Copy link
Member Author

abhi1693 commented Apr 7, 2023

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

@abhi1693
Copy link
Member Author

abhi1693 commented May 5, 2023

Since this hasn't had much traction, we may not need this due to deprecation in #12510

@jeremystretch
Copy link
Member

Agreed; I'm going to punt on this.

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2023
@jeremystretch jeremystretch removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

4 participants