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

Multiselect has no 'delete' option on the values #9524

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

Originally created by @PieterL75 on GitHub (Apr 23, 2024).

Deployment Type

NetBox Cloud

NetBox Version

v4.0-beta1

Python Version

3.8

Steps to Reproduce

Open a device and edit
go to the tags fiels
Add some tags

Expected Behavior

Each tag should have an 'x' so that the tag can be removed from the multiselect

Observed Behavior

no 'x'
image

this seems to be the case on all multivalue fields, and not only tags

Originally created by @PieterL75 on GitHub (Apr 23, 2024). ### Deployment Type NetBox Cloud ### NetBox Version v4.0-beta1 ### Python Version 3.8 ### Steps to Reproduce Open a device and edit go to the tags fiels Add some tags ### Expected Behavior Each tag should have an 'x' so that the tag can be removed from the multiselect ### Observed Behavior no 'x' ![image](https://github.com/netbox-community/netbox/assets/74899468/53d8e5bb-a876-4b37-95c8-a72a3da91993) this seems to be the case on all multivalue fields, and not only tags
adam added the beta label 2025-12-29 20:50:58 +01:00
adam closed this issue 2025-12-29 20:50:58 +01:00
adam commented 2025-12-29 20:50:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 23, 2024):

This is not a bug; it's how Tom-Select works. Selected items can be removed using the delete or backspace keys. Please submit a feature request if you would like to propose an additional mechanism for deleting items.

@jeremystretch commented on GitHub (Apr 23, 2024): This is not a bug; it's how [Tom-Select](https://tom-select.js.org/examples/) works. Selected items can be removed using the delete or backspace keys. Please submit a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature%2Cstatus%3A+needs+triage&projects=&template=feature_request.yaml) if you would like to propose an additional mechanism for deleting items.
adam commented 2025-12-29 20:50:59 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Apr 24, 2024):

It is hard to tell what you guys define as a change or as a bug.
As there was an X in v3, I would assume that there is still an X in v4.

Changing that behaviour is counter productive, I have to release my mouse and press backspace and get my mouse again...
To me, this is a bug/oversight and not a new feature

I checked that TomSelect, and saw the X on the landing page, hence my classification as a bug
image

@PieterL75 commented on GitHub (Apr 24, 2024): It is hard to tell what you guys define as a change or as a bug. As there was an X in v3, I would assume that there is still an X in v4. Changing that behaviour is counter productive, I have to release my mouse and press backspace and get my mouse again... To me, this is a bug/oversight and not a new feature I checked that TomSelect, and saw the X on the landing page, hence my classification as a bug ![image](https://github.com/netbox-community/netbox/assets/74899468/f607c28e-5d81-40c3-9e3d-a91b657bc7fb)
adam commented 2025-12-29 20:50:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 24, 2024):

It is hard to tell what you guys define as a change or as a bug.

I believe the contributing guide is quite clear:

Bug reports are used to call attention to some unintended or unexpected behavior in NetBox, such as when an error occurs or when the result of taking some action is inconsistent with the documentation. Bug reports may not be used to suggest new functionality; please see "feature requests" below if that is your goal.

If you find yourself having difficulty making the distinction for a particular issue, submit is as a feature request.

@jeremystretch commented on GitHub (Apr 24, 2024): > It is hard to tell what you guys define as a change or as a bug. I believe the [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md#bug-reporting-bugs) is quite clear: > Bug reports are used to call attention to some unintended or unexpected behavior in NetBox, such as when an error occurs or when the result of taking some action is inconsistent with the documentation. **Bug reports may not be used to suggest new functionality**; please see "feature requests" below if that is your goal. If you find yourself having difficulty making the distinction for a particular issue, submit is as a feature request.
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 beta
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#9524
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?