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

Improve the form widget for assigning object types for permissions #11416

New Issue
Closed
opened 2025-12-29 21:44:59 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:44:59 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jul 28, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.3.4

Feature type

Change to existing functionality

Proposed functionality

Introduce a new form field field & widget to improve the user experience when modifying object types for a permission. The form field currently looks like this:

Image

This FR proposes adopting an approach similar to how we handle the selection of columns when reconfiguring an object table:

Image

(The ordering of selected options is not significant in this context.)

This should be implemented in a way such that a single form field class can be reused throughout the application as needed.

Use case

The current approach has several drawbacks:

  • Selecting a large number of options can be tedious
  • Mis-clicking within the field can result in accidentally clearing all selections
  • The size of the selection widget is limited and inhibits readability

Adopting the dual-column approach would make the process of adding and removing individual options less error-prone, while preserving the ability to make bulk selections.

Database changes

N/A

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Jul 28, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.3.4 ### Feature type Change to existing functionality ### Proposed functionality Introduce a new form field field & widget to improve the user experience when modifying object types for a permission. The form field currently looks like this: <img width="723" height="195" alt="Image" src="https://github.com/user-attachments/assets/45aaa7ac-1569-42b9-a19b-a1599dd3e520" /> This FR proposes adopting an approach similar to how we handle the selection of columns when reconfiguring an object table: <img width="728" height="468" alt="Image" src="https://github.com/user-attachments/assets/5cbfbf5b-8385-451d-85c6-fc96c553abfa" /> (The ordering of selected options is not significant in this context.) This should be implemented in a way such that a single form field class can be reused throughout the application as needed. ### Use case The current approach has several drawbacks: * Selecting a large number of options can be tedious * Mis-clicking within the field can result in accidentally clearing all selections * The size of the selection widget is limited and inhibits readability Adopting the dual-column approach would make the process of adding and removing individual options less error-prone, while preserving the ability to make bulk selections. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: medium labels 2025-12-29 21:45:00 +01:00
adam closed this issue 2025-12-29 21:45:00 +01:00
adam commented 2025-12-29 21:45:00 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 30, 2025):

it would be neat if you had a search/filter field to easily filter the list of objects to make finding and selecting the desired objects easier/faster.

@ghost commented on GitHub (Jul 30, 2025): it would be neat if you had a search/filter field to easily filter the list of objects to make finding and selecting the desired objects easier/faster.
adam commented 2025-12-29 21:45:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 30, 2025):

I have a lot of cleanup to do, but here's the rough functionality in place:

Image

@jeremystretch commented on GitHub (Jul 30, 2025): I have a lot of cleanup to do, but here's the rough functionality in place: ![Image](https://github.com/user-attachments/assets/1866966a-cc12-433d-b5af-2d9c2064d595)
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 complexity: medium 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#11416
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?