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

Reset dashboard for a selection or all users #8931

New Issue
Closed
opened 2025-12-29 20:42:59 +01:00 by adam · 6 comments
adam commented 2025-12-29 20:42:59 +01:00
Owner
Copy Link

Originally created by @YoucefYousfi on GitHub (Dec 7, 2023).

NetBox version

v3.6.1

Feature type

Change to existing functionality

Proposed functionality

Currently, modifying the default dashboard doesn't take effect for any user that has viewed the dashboard previously. If there is a change on the configuration for the default dashboard, the only way to view it is to reset the dashboard. It would be nice as an admin to have the ability to force reset the dashboard of a selection or all users. By default, users who made changes to their dashboard could be ignored by this reset.

Use case

Without any user interaction, users could take benefit of a default dashboard change. It may be hard to push all users to reset their dashboard when there are a lot of users, and that is for each default dashboard change.

More specifically, this would also allow admins to display things on the dashboard that can dynamically change, though it would probably require for the default dashboard to be editable without restarting Netbox for this specific use case.

Database changes

No response

External dependencies

No response

Originally created by @YoucefYousfi on GitHub (Dec 7, 2023). ### NetBox version v3.6.1 ### Feature type Change to existing functionality ### Proposed functionality Currently, modifying the default dashboard doesn't take effect for any user that has viewed the dashboard previously. If there is a change on the configuration for the default dashboard, the only way to view it is to reset the dashboard. It would be nice as an admin to have the ability to force reset the dashboard of a selection or all users. By default, users who made changes to their dashboard could be ignored by this reset. ### Use case Without any user interaction, users could take benefit of a default dashboard change. It may be hard to push all users to reset their dashboard when there are a lot of users, and that is for each default dashboard change. More specifically, this would also allow admins to display things on the dashboard that can dynamically change, though it would probably require for the default dashboard to be editable without restarting Netbox for this specific use case. ### Database changes _No response_ ### External dependencies _No response_
adam closed this issue 2025-12-29 20:43:00 +01:00
adam commented 2025-12-29 20:43:00 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Dec 8, 2023):

Hi @YoucefYousfi, thanks for this issue. @jeremystretch and I talked through it briefly and we see value in it, but we also would like to see deeper exploration of its implications. For instance, a user who has invested lots of effort in getting their personal dashboard just right might log in one day to find their customizations are gone, replaced with a new version that does not serve their needs as well. How could we mitigate such a violation of the principle of least astonishment?

We would love to hear about how this request might be reconciled with use cases you might not yet have considered.

@jeffgdotorg commented on GitHub (Dec 8, 2023): Hi @YoucefYousfi, thanks for this issue. @jeremystretch and I talked through it briefly and we see value in it, but we also would like to see deeper exploration of its implications. For instance, a user who has invested lots of effort in getting their personal dashboard just right might log in one day to find their customizations are gone, replaced with a new version that does not serve their needs as well. How could we mitigate such a violation of the [principle of least astonishment](https://en.wikipedia.org/wiki/Principle_of_least_astonishment)? We would love to hear about how this request might be reconciled with use cases you might not yet have considered.
adam commented 2025-12-29 20:43:01 +01:00
Author
Owner
Copy Link

@YoucefYousfi commented on GitHub (Dec 8, 2023):

I have thought about this problem as well. I think a simple solution would be to limit the reset to users who use the default dashboard. For users who modified their dashboard, they could either not benefit from the default dashboard changes, or they could be notified that the default dashboard has changed leaving them the choice of keeping theirs or moving to the new default dashboard.

Pushing this idea a bit further, depending on the feasability, users could be asked whether to keep old one, use new one, or even merge dashboards (as in, same widgets on same placement remain unchanged, and new or different widgets can be added at the end of the list of widgets, leaving the user the choice of discarding them when editing their dashboard).

@YoucefYousfi commented on GitHub (Dec 8, 2023): I have thought about this problem as well. I think a simple solution would be to limit the reset to users who use the default dashboard. For users who modified their dashboard, they could either not benefit from the default dashboard changes, or they could be notified that the default dashboard has changed leaving them the choice of keeping theirs or moving to the new default dashboard. Pushing this idea a bit further, depending on the feasability, users could be asked whether to keep old one, use new one, or even merge dashboards (as in, same widgets on same placement remain unchanged, and new or different widgets can be added at the end of the list of widgets, leaving the user the choice of discarding them when editing their dashboard).
adam commented 2025-12-29 20:43:01 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Dec 14, 2023):

One alternative: "saved" dashboards with a dropdown choice list, With the default being available and customised ones.
So when a user saves their dashboard they would get the option of naming it and possibly making it "public" for other users.

This way the "default" dashboard would become a starting point but always be available. People who choose to use the default dashboard would always get the uptodate copy.

@ITJamie commented on GitHub (Dec 14, 2023): One alternative: "saved" dashboards with a dropdown choice list, With the default being available and customised ones. So when a user saves their dashboard they would get the option of naming it and possibly making it "public" for other users. This way the "default" dashboard would become a starting point but always be available. People who choose to use the default dashboard would always get the uptodate copy.
adam commented 2025-12-29 20:43:01 +01:00
Author
Owner
Copy Link

@wriedel commented on GitHub (Jan 19, 2024):

Hi Folks,
just wonder if there is a way to export a dashboard so I can make it the default dashbord ?
I have invested lots of effort in getting a dashboard right for our environment and would like to share it with others.
Maybe an admin could share it and make it available as a "public" dashboard?
It's solved nicely within LibreNMS where I can choose to keep it privat or make it public. The public dashboard name is just prefixed with the username.

@wriedel commented on GitHub (Jan 19, 2024): Hi Folks, just wonder if there is a way to export a dashboard so I can make it the default dashbord ? I have invested lots of effort in getting a dashboard right for our environment and would like to share it with others. Maybe an admin could share it and make it available as a "public" dashboard? It's solved nicely within LibreNMS where I can choose to keep it privat or make it public. The public dashboard name is just prefixed with the username.
adam commented 2025-12-29 20:43:01 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 22, 2024):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 22, 2024): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:43:01 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 21, 2024):

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 (Sep 21, 2024): 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 complexity: medium pending closure status: needs owner topic: UI/UX 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#8931
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?