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

Change table configuration form to be side-by-side #5105

New Issue
Closed
opened 2025-12-29 19:24:16 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:24:16 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jul 27, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.9

Feature type

Change to existing functionality

Proposed functionality

Change the layout of the table configuration forms so that the lists of available and selected columns are side-by-side (rather than one on top of the other).

Use case

Seems like having the columns side-by-side with the "add" and "remove" buttons in between them would feel more natural for the user. It would also be a bit cleaner as the "move up" and "move down" buttons would only be below the "selected columns" list.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Jul 27, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.9 ### Feature type Change to existing functionality ### Proposed functionality Change the layout of the table configuration forms so that the lists of available and selected columns are side-by-side (rather than one on top of the other). ### Use case Seems like having the columns side-by-side with the "add" and "remove" buttons in between them would feel more natural for the user. It would also be a bit cleaner as the "move up" and "move down" buttons would only be below the "selected columns" list. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:24:16 +01:00
adam closed this issue 2025-12-29 19:24:16 +01:00
adam commented 2025-12-29 19:24:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 6, 2021):

Fixed in the feature branch for the upcoming v3.0 release.

@jeremystretch commented on GitHub (Aug 6, 2021): Fixed in the `feature` branch for the upcoming v3.0 release.
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#5105
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?