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

Allow "Long Text" fields to be collapsible #10871

New Issue
Closed
opened 2025-12-29 21:37:02 +01:00 by adam · 6 comments
adam commented 2025-12-29 21:37:02 +01:00
Owner
Copy Link

Originally created by @SchoolGuy on GitHub (Mar 11, 2025).

NetBox version

v4.2.4

Feature type

Other

Proposed functionality

At work, I would like to be able to collapse custom fields of type "Long Text".

Use case

The NetBox instance at work is supposed to store the output of lspci inside a custom field so that NetBox users can search through the output. Since the output can be quite long with larger machines it is desired that the text is collapsible.

Database changes

I don't believe that this needs database changes since this should be a UI only feature.

External dependencies

No response

Originally created by @SchoolGuy on GitHub (Mar 11, 2025). ### NetBox version v4.2.4 ### Feature type Other ### Proposed functionality At work, I would like to be able to collapse custom fields of type "Long Text". ### Use case The NetBox instance at work is supposed to store the output of lspci inside a custom field so that NetBox users can search through the output. Since the output can be quite long with larger machines it is desired that the text is collapsible. ### Database changes I don't believe that this needs database changes since this should be a UI only feature. ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:37:02 +01:00
adam closed this issue 2025-12-29 21:37:02 +01:00
adam commented 2025-12-29 21:37:03 +01:00
Author
Owner
Copy Link

@SchoolGuy commented on GitHub (Mar 11, 2025):

CC @hreinecke

@SchoolGuy commented on GitHub (Mar 11, 2025): CC @hreinecke
adam commented 2025-12-29 21:37:04 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Mar 20, 2025):

@SchoolGuy could you please detail how this would work? Would this be a global control, a preference, etc? Which pages/views would this apply to? Can you mock up some wireframes?

@bctiemann commented on GitHub (Mar 20, 2025): @SchoolGuy could you please detail how this would work? Would this be a global control, a preference, etc? Which pages/views would this apply to? Can you mock up some wireframes?
adam commented 2025-12-29 21:37:04 +01:00
Author
Owner
Copy Link

@SchoolGuy commented on GitHub (Mar 20, 2025):

I have actually never done a single wireframe in my life. I'll take this as an excuse to learn about it. How do you do wireframes? Could you give me some pointers?

I am in general very open about the exact implementation of this. This feature request comes from the fact that we just have custom fields that contain the full output of lspci which makes the page of the device quite unusable if the field is populated.

@SchoolGuy commented on GitHub (Mar 20, 2025): I have actually never done a single wireframe in my life. I'll take this as an excuse to learn about it. How do you do wireframes? Could you give me some pointers? I am in general very open about the exact implementation of this. This feature request comes from the fact that we just have custom fields that contain the full output of lspci which makes the page of the device quite unusable if the field is populated.
adam commented 2025-12-29 21:37:05 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Mar 20, 2025):

It doesn't need to be formal, just a photoshopped version of a page where this would be relevant so we can see what it would look like.

@bctiemann commented on GitHub (Mar 20, 2025): It doesn't need to be formal, just a photoshopped version of a page where this would be relevant so we can see what it would look like.
adam commented 2025-12-29 21:37:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 28, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Mar 28, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:37:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 4, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Apr 4, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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: revisions needed 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#10871
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?