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 default table configuration #4436

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

Originally created by @TomGrozev on GitHub (Jan 4, 2021).

Environment

  • Python version: 3.7.3
  • NetBox version: 2.10.x

Proposed Functionality

Be able to set in the admin panel the default table configuration for columns for all users. This would be on a per model basis, e.g. virtual machines could have a different configuration to vlans. If a user customises the column configuration it would override the default.

Use Case

This would allow for a default view for new users without having to change the configuration. This is especially useful for custom fields in tables and hence closesly related to #5344 and #5460.

Database Changes

This could be done with a new model but would be much more efficient to simply store an ordered list in the associated model for the default configuration. Due to the database change this would likely be a candidate for 2.11.

External Dependencies

N/A

Also, I am happy to have this assigned to me.

Originally created by @TomGrozev on GitHub (Jan 4, 2021). <!-- 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 start a discussion instead: https://github.com/netbox-community/netbox/discussions 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.10.x <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Be able to set in the admin panel the default table configuration for columns for all users. This would be on a per model basis, e.g. virtual machines could have a different configuration to vlans. If a user customises the column configuration it would override the default. <!-- 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 This would allow for a default view for new users without having to change the configuration. This is especially useful for custom fields in tables and hence closesly related to #5344 and #5460. <!-- 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 This could be done with a new model but would be much more efficient to simply store an ordered list in the associated model for the default configuration. Due to the database change this would likely be a candidate for 2.11. <!-- 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 N/A Also, I am happy to have this assigned to me.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 18:35:57 +01:00
adam closed this issue 2025-12-29 18:35:58 +01:00
adam commented 2025-12-29 18:35:58 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 5, 2021):

If we went down this route, I would say it would be better to store the configuration in configuration.py. I don't think it makes sense to make a database query for each page view with a table when the query itself would be rather static.

The problem is each table has different columns so it would need to be a list in a dict or similar for this to work (just off the top of my head).

That said, we already have enough on our plate so someone would have to volunteer to own this.

@DanSheps commented on GitHub (Jan 5, 2021): If we went down this route, I would say it would be better to store the configuration in configuration.py. I don't think it makes sense to make a database query for each page view with a table when the query itself would be rather static. The problem is each table has different columns so it would need to be a list in a dict or similar for this to work (just off the top of my head). That said, we already have enough on our plate so someone would have to volunteer to own this.
adam commented 2025-12-29 18:35:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 5, 2021):

IMO this exceeds the reasonable ratio for developer burden to user value. If you really need a way to set default views for new users, it seems like a custom script would work just fine.

@jeremystretch commented on GitHub (Jan 5, 2021): IMO this exceeds the reasonable ratio for developer burden to user value. If you really need a way to set default views for new users, it seems like a custom script would work just fine.
adam commented 2025-12-29 18:35:59 +01:00
Author
Owner
Copy Link

@TomGrozev commented on GitHub (Jan 6, 2021):

@DanSheps I believe you are right, a configuration option would actually be much better.

I will give it a go and make a PR if you assign the issue to me.

@TomGrozev commented on GitHub (Jan 6, 2021): @DanSheps I believe you are right, a configuration option would actually be much better. I will give it a go and make a PR if you assign the issue to me.
adam commented 2025-12-29 18:35:59 +01:00
Author
Owner
Copy Link

@xkilian commented on GitHub (Jan 6, 2021):

I would personally love to see this go forward, as it may be more burden for devs, but for dozens of users, each having to customize their views to match company documentation/traning material is a bit of a usability problem. As I am sure most companies will make use of custom fields for various needs and should/will want to make that data more accessible. I understand that a custom script could set these values for users, so there is a workaround. Thank you once again fro the excellent work.

@xkilian commented on GitHub (Jan 6, 2021): I would personally love to see this go forward, as it may be more burden for devs, but for dozens of users, each having to customize their views to match company documentation/traning material is a bit of a usability problem. As I am sure most companies will make use of custom fields for various needs and should/will want to make that data more accessible. I understand that a custom script could set these values for users, so there is a workaround. Thank you once again fro the excellent work.
adam commented 2025-12-29 18:35:59 +01:00
Author
Owner
Copy Link

@exc91 commented on GitHub (Jan 21, 2021):

Tell me please is this feature available in release Netbox 2.10.3?
I already have installed Netbox 2.10.3 and it's really great product. But I didn't find how to make custom fields take a place to the table Devices with button Configure on a right top in my case...

@exc91 commented on GitHub (Jan 21, 2021): Tell me please is this feature available in release Netbox 2.10.3? I already have installed Netbox 2.10.3 and it's really great product. But I didn't find how to make custom fields take a place to the table Devices with button Configure on a right top in my case...
adam commented 2025-12-29 18:35:59 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 19, 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.

@stale[bot] commented on GitHub (Mar 19, 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 18:35:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 14, 2021):

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 (Apr 14, 2021): 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#4436
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?