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

Convert table preferences form to use two selection fields #4720

New Issue
Closed
opened 2025-12-29 19:19:51 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:19:51 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Apr 4, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.10.8

Feature type

Change to existing functionality

Proposed functionality

The user table preferences form currently shows a single multiple selection field listing all available columns. Selected columns are displayed within the table:

table_config_form

This FR proposes to instead use two side-by-side multiple selection fields: one for available columns and one for selected columns. The Django admin UI has a good example of this:

django_admin_form

Use case

Using two separate selection fields should provide a smoother and more intuitive user experience.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Apr 4, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.10.8 ### Feature type Change to existing functionality ### Proposed functionality The user table preferences form currently shows a single multiple selection field listing all available columns. Selected columns are displayed within the table: ![table_config_form](https://user-images.githubusercontent.com/13487278/113519669-ac499c80-955b-11eb-8159-e34174e42e3d.png) This FR proposes to instead use two side-by-side multiple selection fields: one for available columns and one for selected columns. The Django admin UI has a good example of this: ![django_admin_form](https://user-images.githubusercontent.com/13487278/113519726-12362400-955c-11eb-8a3d-969c54139ce5.png) ### Use case Using two separate selection fields should provide a smoother and more intuitive user experience. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:19:51 +01:00
adam closed this issue 2025-12-29 19:19:52 +01:00
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#4720
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?