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

Export Color name instead of of Hex code #18843

Open
dfex opened this issue Mar 7, 2025 · 4 comments
Open

Export Color name instead of of Hex code #18843

dfex opened this issue Mar 7, 2025 · 4 comments
Assignees
Labels
complexity: low Requires minimal effort to implement status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@dfex
Copy link
Contributor

dfex commented Mar 7, 2025

NetBox version

v4.2.5-Docker-3.2.0

Feature type

Change to existing functionality

Proposed functionality

Hello Netbox legends!

I'm exporting the Cables view to CSV for my field techs to go and patch interfaces.

One thing that confuses them (among many) is that Netbox exports the Colour column as Hex Values:
Image

It would be great if this could export the Color name (that is displayed in the color picker drop-down) instead:
Image

Thanks!

Ben

Use case

Would allow netbox admins to export Cable views as patching schedules for electrical/cabling contractors to execute.

Database changes

Possibly, yes - from what I can see of the API data, only the hex code is stored, not the color name

External dependencies

None

@dfex dfex added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Mar 7, 2025
@jeremystretch
Copy link
Member

Storing the actual RGB value in the database has some utility, so I think we want to keep it. However, we could add an optional field on the tables with color fields to include the name of the color as well.

We could potentially also support using the color names for bulk import as well, by introducing an optional color_name field. That should probably be a separate FR though.

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation complexity: low Requires minimal effort to implement and removed status: needs triage This issue is awaiting triage by a maintainer labels Mar 13, 2025
@dfex
Copy link
Contributor Author

dfex commented Mar 14, 2025

I'm happy to own this one and get a PR raised

@bctiemann bctiemann added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Mar 14, 2025
@1024834
Copy link

1024834 commented Mar 18, 2025

We could potentially also support using the color names for bulk import as well, by introducing an optional color_name field. That should probably be a separate FR though.

Requested in #18936

@bctiemann
Copy link
Contributor

@dfex if you can handle #18936 as well, please comment in that FR and we can assign it to you. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: low Requires minimal effort to implement 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

4 participants