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

Support custom fields in user table configuration #4270

New Issue
Closed
opened 2025-12-29 18:34:20 +01:00 by adam · 7 comments
adam commented 2025-12-29 18:34:20 +01:00
Owner
Copy Link

Originally created by @ypid on GitHub (Nov 13, 2020).

Environment

  • Python version: 3.7.3
  • NetBox version: 2.9.9 and develop-2.10

Proposed Functionality

Support custom fields to be included in list views by making them user configurable (table configuration).

Use Case

A custom field might be important enough to see it in various list views. This is important to be able to compare it with other objects of the same model. Also, when doing quality assurance, one might want to sort on custom field and then use the bulk edit to normalize the values.

This has been reported before but got closed:

  • #492 which is related but did not cover this feature in its initial request, but later in the discussion. Seems it has been overlooked when it got closed.
  • #2028 and #2460 asked exactly the same but got closed by #492.
  • #1997 Was not clear if #492 was meant.

Cc: @eloquentheit, @sampl3x, @mryauch, @hanej, @lesinigo, @Grokzen,

Database Changes

I assume not now that #4878 is done.

External Dependencies

None.

Originally created by @ypid on GitHub (Nov 13, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/g/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7.3 * NetBox version: 2.9.9 and [develop-2.10](https://github.com/netbox-community/netbox/commit/f3f3993963bac7104edc51bd777887462e7dd5af) <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Support custom fields to be included in list views by making them user configurable (table configuration). <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case A custom field might be important enough to see it in various list views. This is important to be able to compare it with other objects of the same model. Also, when doing quality assurance, one might want to sort on custom field and then use the bulk edit to normalize the values. This has been reported before but got closed: * #492 which is related but did not cover this feature in its initial request, but later in the discussion. Seems it has been overlooked when it got closed. * #2028 and #2460 asked exactly the same but got closed by #492. * #1997 Was not clear if #492 was meant. Cc: @eloquentheit, @sampl3x, @mryauch, @hanej, @lesinigo, @Grokzen, <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes I assume not now that #4878 is done. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 18:34:20 +01:00
adam closed this issue 2025-12-29 18:34:20 +01:00
adam commented 2025-12-29 18:34:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 16, 2020):

FYI this needs to wait until v2.10 has been released (because of the changes in #4878). @ypid would you like to volunteer to take on this work once is can begin?

@jeremystretch commented on GitHub (Nov 16, 2020): FYI this needs to wait until v2.10 has been released (because of the changes in #4878). @ypid would you like to volunteer to take on this work once is can begin?
adam commented 2025-12-29 18:34:21 +01:00
Author
Owner
Copy Link

@ypid commented on GitHub (Nov 16, 2020):

Count me in :) You can assign me to this issue. I am already watching for new releases and am going to pick this issue up once 2.10 drops. Keep up the awesome work!

Edit: Looks like I was too slow. TomGrozev jumped in and did it before I had the chance.

@ypid commented on GitHub (Nov 16, 2020): Count me in :) You can assign me to this issue. I am already watching for new releases and am going to pick this issue up once 2.10 drops. Keep up the awesome work! Edit: Looks like I was too slow. TomGrozev jumped in and did it before I had the chance.
adam commented 2025-12-29 18:34:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 16, 2020):

Cool. Marking this as blocked for now pending the v2.10 release.

@jeremystretch commented on GitHub (Nov 16, 2020): Cool. Marking this as blocked for now pending the v2.10 release.
adam commented 2025-12-29 18:34:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 21, 2020):

@TomGrozev would you like to take ownership of this issue so that your PR can be reviewed?

@jeremystretch commented on GitHub (Dec 21, 2020): @TomGrozev would you like to take ownership of this issue so that your PR can be reviewed?
adam commented 2025-12-29 18:34:21 +01:00
Author
Owner
Copy Link

@TomGrozev commented on GitHub (Dec 21, 2020):

@jeremystretch Sure.

@TomGrozev commented on GitHub (Dec 21, 2020): @jeremystretch Sure.
adam commented 2025-12-29 18:34:21 +01:00
Author
Owner
Copy Link

@hyudra commented on GitHub (Mar 8, 2021):

May I ask that, will this feature be one of v2.11 milestone?

@hyudra commented on GitHub (Mar 8, 2021): May I ask that, will this feature be one of v2.11 milestone?
adam commented 2025-12-29 18:34:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2021):

Yes, this has been implemented for v2.11.

@jeremystretch commented on GitHub (Mar 30, 2021): Yes, this has been implemented for v2.11.
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#4270
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?