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

Ability To Export Dashboard Widget Layouts #11746

New Issue
Open
opened 2025-12-29 21:49:24 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:49:24 +01:00
Owner
Copy Link

Originally created by @mr1716 on GitHub (Oct 19, 2025).

NetBox version

v4.4.4

Feature type

New functionality

Proposed functionality

What this would do is have a way to save the desired Dashboard Widget format in a format that an admin could use to update the constants.py file. This would allow users to copy the exported format of the new dashboard layout to then write to the file, rather than having to change it manually after updating the UI.

Use case

When admins want to change the default dashboard widget layout to highlight different aspects than is the default, this would make it significantly faster to set the default dashboard.

Specific examples would be if I created a new plugin to capture BGP information and wanted to add a plugin to the Dashboard showing that BGP information, creating the widgets as a default isn’t the easiest thing to write or test. Being able to export the dashboard as I want and then copy/paste to the constants.py file would save time.

Database changes

None?

External dependencies

None??

Originally created by @mr1716 on GitHub (Oct 19, 2025). ### NetBox version v4.4.4 ### Feature type New functionality ### Proposed functionality What this would do is have a way to save the desired Dashboard Widget format in a format that an admin could use to update the constants.py file. This would allow users to copy the exported format of the new dashboard layout to then write to the file, rather than having to change it manually after updating the UI. ### Use case When admins want to change the default dashboard widget layout to highlight different aspects than is the default, this would make it significantly faster to set the default dashboard. Specific examples would be if I created a new plugin to capture BGP information and wanted to add a plugin to the Dashboard showing that BGP information, creating the widgets as a default isn’t the easiest thing to write or test. Being able to export the dashboard as I want and then copy/paste to the constants.py file would save time. ### Database changes None? ### External dependencies None??
adam added the type: featurestatus: backlogcomplexity: low labels 2025-12-29 21:49:24 +01:00
adam commented 2025-12-29 21:49:25 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Nov 3, 2025):

We discussed this in our FR review meeting. A few implementation approaches came up:

  1. Management command: outputs Python code ready for configuration.py
  2. Copy from user: Admin UI option to set default dashboard to match a specific user's layout
  3. Web UI export/import: If supporting export in the UI, should also support import

We've moved this to the backlog while we consider the best approach. The management command option seems most appropriate, to me, given the audience (admins) and operation frequency (occasional), but the UI-based approaches have appeal for discoverability.

@jnovinger commented on GitHub (Nov 3, 2025): We discussed this in our FR review meeting. A few implementation approaches came up: 1. Management command: outputs Python code ready for `configuration.py` 2. Copy from user: Admin UI option to set default dashboard to match a specific user's layout 3. Web UI export/import: If supporting export in the UI, should also support import We've moved this to the backlog while we consider the best approach. The management command option seems most appropriate, to me, given the audience (admins) and operation frequency (occasional), but the UI-based approaches have appeal for discoverability.
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 complexity: low status: backlog 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#11746
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?