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

Breadcumb under custom script or report #7208

Closed
jk-onnet opened this issue Sep 8, 2021 · 0 comments
Closed

Breadcumb under custom script or report #7208

jk-onnet opened this issue Sep 8, 2021 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@jk-onnet
Copy link

jk-onnet commented Sep 8, 2021

NetBox version

v3.0.1

Feature type

Change to existing functionality

Proposed functionality

Adding breadcumb on top of custom script as well as custom report.

Use case

In new version, I observed when clicking the core object, the breadcumb is disappear unless clicking the core object item.
However, clicking the custom script/report item, the breadcumb on top of custom script is not there. I'm not sure is it a intended behavior.

The tab UI has changed from horizontal to vertical, it might difficult to navigate from one script to another script.
Instead of clicking the back button of the browser or find the script/report object on the vertical UI (scroll to bottom), a breadcumb will help us better for development.

Thank you for the amazing UI and tool.

Database changes

None

External dependencies

None

@jk-onnet jk-onnet added the type: feature Introduction of new functionality to the application label Sep 8, 2021
@jk-onnet jk-onnet changed the title Breadcumb under custom script Breadcumb under custom script or report Sep 8, 2021
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Sep 15, 2021
@jeremystretch jeremystretch self-assigned this Sep 15, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants