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

Display unnamed devices consistently #2634

Closed
candlerb opened this issue Nov 30, 2018 · 0 comments
Closed

Display unnamed devices consistently #2634

candlerb opened this issue Nov 30, 2018 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@candlerb
Copy link
Contributor

Environment

  • Python version: 3.5.2
  • NetBox version: 2.4.8

Steps to Reproduce

  • Create an unnamed device; assign it to a rack and position
  • Create another unnamed device; assign it to a rack but no position
  • View these pages:
    • /dcim/devices/X/
    • /dcim/racks/Y/ (where rack Y contains the devices)

Expected Behavior

Consistent display: always show the model number in place of the missing name.

Observed Behavior

  • In the device page, it displays the model number (Good)
  • In the list of "Unracked devices" in the rack page, it displays the model number (Good)
  • But in the rack graphical display, it displays the role rather than the model

This means you see (e.g.) "Switch" rather than "2960-X", which I think is less helpful. The role is already visible in the colour.

Workaround: you can get the model number if you hover over the item, but you can't see as much at a glance.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Dec 4, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
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