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

Front and Rear Ports do not highlight connected rows #16039

Open
DanSheps opened this issue May 8, 2024 · 1 comment · May be fixed by #16044
Open

Front and Rear Ports do not highlight connected rows #16039

DanSheps opened this issue May 8, 2024 · 1 comment · May be fixed by #16044
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation topic: UI/UX User interface or user experience related work type: bug A confirmed report of unexpected behavior in the application

Comments

@DanSheps
Copy link
Member

DanSheps commented May 8, 2024

Deployment Type

Self-hosted

NetBox Version

v4.0.0

Python Version

3.10

Steps to Reproduce

  1. Create 2 interfaces
  2. Create 2 Rear Ports
  3. Create 2 Front Ports
  4. Connect 2 interfaces to 2 Front Ports
  5. Connect 2 rear ports together
  6. View Front Ports and Rear Ports

Expected Behavior

Row to be highlighted

Observed Behavior

Row is not highlighted

@DanSheps DanSheps added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels May 8, 2024
@DanSheps DanSheps self-assigned this May 8, 2024
@DanSheps
Copy link
Member Author

DanSheps commented May 8, 2024

Root cause appears to be "green" class no longer exists and data fields are not set on these ports as they are with the interface field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation topic: UI/UX User interface or user experience related work type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants