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

UI improvement for Custom field selection type #5435

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

Originally created by @hagbarddenstore on GitHub (Sep 28, 2021).

NetBox version

v3.0.v

Feature type

Change to existing functionality

Proposed functionality

Generate one textbox per item via Javascript and then concatenate all textboxes into a string again when submitting the custom fields form.

This could be further enhanced by allowing drag'n'drop of the textboxes to allow ordering the values.

Use case

It's horrible to edit a comma-separated list of items if there are more than 3-4 items. To be able to fully utilize the selection type a UI change is required.

Database changes

None

External dependencies

This might require a Javascript library, not sure which are needed and which are already included in Netbox.

Originally created by @hagbarddenstore on GitHub (Sep 28, 2021). ### NetBox version v3.0.v ### Feature type Change to existing functionality ### Proposed functionality Generate one textbox per item via Javascript and then concatenate all textboxes into a string again when submitting the custom fields form. This could be further enhanced by allowing drag'n'drop of the textboxes to allow ordering the values. ### Use case It's horrible to edit a comma-separated list of items if there are more than 3-4 items. To be able to fully utilize the selection type a UI change is required. ### Database changes None ### External dependencies This might require a Javascript library, not sure which are needed and which are already included in Netbox.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:27:55 +01:00
adam closed this issue 2025-12-29 19:27:55 +01:00
adam commented 2025-12-29 19:27:55 +01:00
Author
Owner
Copy Link

@snowie-swe commented on GitHub (Sep 28, 2021):

I believe this would limit the amount of request from regular none coding users.
Tabs and section boxes is needed to keep track of multiple custom fields, this would cover the majority of our own cases.
Then it would be very simple to add things like Patch windows, SLA etc etc.

@snowie-swe commented on GitHub (Sep 28, 2021): I believe this would limit the amount of request from regular none coding users. Tabs and section boxes is needed to keep track of multiple custom fields, this would cover the majority of our own cases. Then it would be very simple to add things like Patch windows, SLA etc etc.
adam commented 2025-12-29 19:27:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 28, 2021):

@hagbarddenstore would you like to volunteer to come up with a proof of concept?

@jeremystretch commented on GitHub (Sep 28, 2021): @hagbarddenstore would you like to volunteer to come up with a proof of concept?
adam commented 2025-12-29 19:27:57 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (Sep 28, 2021):

@jeremystretch Absolutely!

@hagbarddenstore commented on GitHub (Sep 28, 2021): @jeremystretch Absolutely!
adam commented 2025-12-29 19:27:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 7, 2021):

@hagbarddenstore have you been able to make any progress with this?

@jeremystretch commented on GitHub (Oct 7, 2021): @hagbarddenstore have you been able to make any progress with this?
adam commented 2025-12-29 19:28:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 28, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 28, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:28:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 28, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 28, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#5435
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?