starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add color field to front/rear ports #3006

New Issue
Closed
opened 2025-12-29 18:24:40 +01:00 by adam · 7 comments
adam commented 2025-12-29 18:24:40 +01:00
Owner
Copy Link

Originally created by @williamwu0220 on GitHub (Nov 8, 2019).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.7.3
  • NetBox version: 2.6.7

Proposed Functionality

Using color keystones makes data center management more convenient, just like this:
https://imgur.com/a/P8izFXW
Since cables can be assigned color attributes in NetBox, I think it would be a big plus if front ports have this attributes as well. :)

Use Case

For example, in our data center, we use yellow keystones denoting they're used by ip phone system, while green keystones means they're used by wireless system.

Database Changes

After digging into source code, I think we can add ColorField in FrontPort class.

External Dependencies

No.

Originally created by @williamwu0220 on GitHub (Nov 8, 2019). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.7.3 * NetBox version: 2.6.7 ### Proposed Functionality Using color keystones makes data center management more convenient, just like this: https://imgur.com/a/P8izFXW Since cables can be assigned color attributes in NetBox, I think it would be a big plus if front ports have this attributes as well. :) ### Use Case For example, in our data center, we use yellow keystones denoting they're used by ip phone system, while green keystones means they're used by wireless system. ### Database Changes After digging into source code, I think we can add ColorField in FrontPort class. ### External Dependencies No.
adam added the status: acceptedtype: feature labels 2025-12-29 18:24:40 +01:00
adam closed this issue 2025-12-29 18:24:40 +01:00
adam commented 2025-12-29 18:24:40 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Nov 12, 2019):

I am curious about this feature though, do you have any idea to add this?
Is it like add color column next to "Connection" in front ports list?
Screen Shot 2019-11-12 at 9 10 56 AM

@kobayashi commented on GitHub (Nov 12, 2019): I am curious about this feature though, do you have any idea to add this? Is it like add color column next to "Connection" in front ports list? ![Screen Shot 2019-11-12 at 9 10 56 AM](https://user-images.githubusercontent.com/8712070/68678980-0132e000-052d-11ea-802d-b0ed49e8f532.png)
adam commented 2025-12-29 18:24:41 +01:00
Author
Owner
Copy Link

@williamwu0220 commented on GitHub (Nov 13, 2019):

TL;DR:

Yes, I think it would be good if we can see each color column directly in front ports list, just like cable list does:

image

Further more, It would be even more better if we can see each front panel color when tracing a cable linking:

image

Detailed Description

Let me describe how we tracing cable linking in our environment. When an equipment needs connect to internet, we check the steps below:

  1. Findout the location id of telecommunications outlet and its associated code via floor plan:
    image
    or do on-site confirming:
    image

  2. Go to data center finding out corresponding patch panel and keystone, double checking if color-code matched:
    image

  3. Finally, according manual mantained mapping table, we can trace the far end interface port:
    image

So, it's really helpful if front ports have color columns. ;)

@williamwu0220 commented on GitHub (Nov 13, 2019): TL;DR: ====== Yes, I think it would be good if we can see each color column directly in front ports list, just like cable list does: ![image](https://user-images.githubusercontent.com/41606/68735134-b0e47c80-0617-11ea-8daf-10d15686afdb.png) Further more, It would be even more better if we can see each front panel color when tracing a cable linking: ![image](https://user-images.githubusercontent.com/41606/68735410-7f1fe580-0618-11ea-9411-44c638ef1a78.png) Detailed Description =================== Let me describe how we tracing cable linking in our environment. When an equipment needs connect to internet, we check the steps below: 1. Findout the location id of telecommunications outlet and its associated code via floor plan: ![image](https://user-images.githubusercontent.com/41606/68738686-e9895380-0621-11ea-874d-8146f1ba48e2.png) or do on-site confirming: ![image](https://user-images.githubusercontent.com/41606/68738785-29e8d180-0622-11ea-929f-93374cac0e4e.png) 2. Go to data center finding out corresponding patch panel and keystone, double checking if color-code matched: ![image](https://user-images.githubusercontent.com/41606/68739027-cf9c4080-0622-11ea-9dc1-d3ff98aaec14.png) 3. Finally, according manual mantained mapping table, we can trace the far end interface port: ![image](https://user-images.githubusercontent.com/41606/68739198-3cafd600-0623-11ea-8b1a-2ee1ea19e30a.png) So, it's really helpful if front ports have color columns. ;)
adam commented 2025-12-29 18:24:41 +01:00
Author
Owner
Copy Link

@williamwu0220 commented on GitHub (Dec 13, 2019):

Hi,
Do I need provide more detail usage scenarios? I'm waiting this feature for adopting netbox in our data center. :)

@williamwu0220 commented on GitHub (Dec 13, 2019): Hi, Do I need provide more detail usage scenarios? I'm waiting this feature for adopting netbox in our data center. :)
adam commented 2025-12-29 18:24:41 +01:00
Author
Owner
Copy Link

@williamwu0220 commented on GitHub (Dec 26, 2019):

Hi,
I'm willing to pick up this task, but I need to know if this feature request is acceptable. ;)

@williamwu0220 commented on GitHub (Dec 26, 2019): Hi, I'm willing to pick up this task, but I need to know if this feature request is acceptable. ;)
adam commented 2025-12-29 18:24:41 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Dec 26, 2019):

Thank you @williamwu0220
This issue is accepted.

@kobayashi commented on GitHub (Dec 26, 2019): Thank you @williamwu0220 This issue is accepted.
adam commented 2025-12-29 18:24:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 23, 2020):

@williamwu0220 have you made any progress on this? Should I remove you as the assigned owner?

@jeremystretch commented on GitHub (Jan 23, 2020): @williamwu0220 have you made any progress on this? Should I remove you as the assigned owner?
adam commented 2025-12-29 18:24:41 +01:00
Author
Owner
Copy Link

@williamwu0220 commented on GitHub (Feb 4, 2020):

Sorry, busy for works these days, I'll work on this issue soon :)

@williamwu0220 commented on GitHub (Feb 4, 2020): Sorry, busy for works these days, I'll work on this issue soon :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3006
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?