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

Add Color Picker for New 'Tag' Feature #1910

New Issue
Closed
opened 2025-12-29 17:20:17 +01:00 by adam · 6 comments
adam commented 2025-12-29 17:20:17 +01:00
Owner
Copy Link

Originally created by @WilliamMarti on GitHub (Aug 7, 2018).

Originally assigned to: @lampwins on GitHub.

Environment

Python version: Python v3.5.2
NetBox version: v2.4.1

Proposed Functionality

Add Color picker, similar to what currently exists with 'Device Roles' already.

Use Case

Currently all tags have a grey background, would be helpful if we could more quickly visually discern which is which.

Database Changes

Assuming we need a new field for the Tag model.

External Dependencies

No new external dependencies required.

Originally created by @WilliamMarti on GitHub (Aug 7, 2018). Originally assigned to: @lampwins on GitHub. ### Environment Python version: Python v3.5.2 NetBox version: v2.4.1 ### Proposed Functionality Add Color picker, similar to what currently exists with 'Device Roles' already. ### Use Case Currently all tags have a grey background, would be helpful if we could more quickly visually discern which is which. ### Database Changes Assuming we need a new field for the Tag model. ### External Dependencies No new external dependencies required.
adam added the status: acceptedtype: feature labels 2025-12-29 17:20:17 +01:00
adam closed this issue 2025-12-29 17:20:18 +01:00
adam commented 2025-12-29 17:20:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2018):

Assuming we need a new field for the Tag model.

We're actually using the stock Tag model from django-taggit. We would need to implement our own model inheriting from TagBase. Should be fairly straightforward with a migration though, I think.

@jeremystretch commented on GitHub (Aug 7, 2018): > Assuming we need a new field for the Tag model. We're actually using the stock Tag model from [django-taggit](https://github.com/alex/django-taggit/blob/master/taggit/models.py#L79). We would need to implement our own model inheriting from TagBase. Should be fairly straightforward with a migration though, I think.
adam commented 2025-12-29 17:20:19 +01:00
Author
Owner
Copy Link

@iDemonix commented on GitHub (Aug 23, 2018):

Would this functionality be in the Django admin area, or within the Netbox UI itself?

@iDemonix commented on GitHub (Aug 23, 2018): Would this functionality be in the Django admin area, or within the Netbox UI itself?
adam commented 2025-12-29 17:20:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 23, 2018):

@iDemonix it would be implemented in the regular frontend.

@jeremystretch commented on GitHub (Aug 23, 2018): @iDemonix it would be implemented in the regular frontend.
adam commented 2025-12-29 17:20:19 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Jan 8, 2019):

Doesn't we could use Select2 for this? We could use the "Multi-select boxes (pillbox)".

@tb-killa commented on GitHub (Jan 8, 2019): Doesn't we could use Select2 for this? We could use the "Multi-select boxes (pillbox)".
adam commented 2025-12-29 17:20:19 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Jan 8, 2019):

@tb-killa yes the UI portion will be taken care of by Select2. In fact this is already implemented in the select2-ui branch.

However, adding color to tags will require more effort and will be implemented after select2 in accordance with this issue.

@lampwins commented on GitHub (Jan 8, 2019): @tb-killa yes the UI portion will be taken care of by Select2. In fact this is already implemented in the `select2-ui` branch. However, adding color to tags will require more effort and will be implemented after select2 in accordance with this issue.
adam commented 2025-12-29 17:20:19 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Feb 22, 2019):

Implemented in the develop-2.6 branch.

@lampwins commented on GitHub (Feb 22, 2019): Implemented in the develop-2.6 branch.
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#1910
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?