Skip to content

Device Name should not contain the asset tag when viewing from rack #8092

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

Closed
bitcollector1 opened this issue Dec 17, 2021 · 0 comments
Closed
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@bitcollector1
Copy link

NetBox version

v3.1.1

Feature type

Change to existing functionality

Proposed functionality

There is not enough room in the rack view to include the asset tag in the name. It makes it so I can't see the slots for the parent/child relationship, i.e. drive bays. It would be great if you could go back to the previous implementation of the rack view where just the device name is represented.

Use case

Here is an example of what things look like after the upgrade, the info runs off the screen due to space limitations.

Screen Shot 2021-12-16 at 4 04 11 PM

Database changes

No response

External dependencies

No response

@bitcollector1 bitcollector1 added the type: feature Introduction of new functionality to the application label Dec 17, 2021
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Dec 18, 2021
@jeremystretch jeremystretch self-assigned this Dec 18, 2021
@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application and removed type: feature Introduction of new functionality to the application labels Dec 18, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 19, 2022
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: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants