-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in deleting widgets #9122
Comments
Thanks @Guddetisandeep. I'm looking at this issue. Let me know if you discovered more information that could be helpful for recreating it. I'll let you know if I can find anything. Thanks! |
Ok, it seems like the problem is that we don't display user's dashboards so you can't drill down to each user dashboard that contains the widget and remove it. How would you expect this to work? Would you really want to manually visit possibly tens of user's dashboards to remove the widget from the dashboard or would you want to some other way to remove them in bulk? |
FYI, this is how the widget sets (dashboard) looks in the backend:
|
When a group dashboard is created under a specific MiqGroup, and a user visits the dashboard for the first time, a user-specific dashboard is created that duplicates the main group dashboard. If there are ten users visiting dashboard it creates ten user-specific dashboards duplicating the main group dashboard. The widgets are set to refresh every hour, so whenever any widget stops refreshing, we replace that widget with a new one. However, when I try to delete the old widget by removing it from the main group dashboard, it results in an error indicating that this widget is present in user-specific dashboards. I believe that if a group is created, all users of that particular group should be able to access that dashboard. Therefore, duplicating the group dashboard for each user might not be necessary. Changes made to the group dashboard should be reflected across all user dashboards within that group. If there are tens or hundreds of users, manually removing the widget from each user's dashboard is a time-consuming process. So, I think if the process of duplicating the group dashboard to create user-specific dashboards is stopped, we would be able to delete widgets without encountering errors. |
Steps to reproduce:
|
So, it looks like the solution could be any one of the following
|
I think option 3 would be beneficial. This way, if we remove a widget from the main dashboard and try to delete it, it should be deleted and any user dashboards referencing it should be cleaned up to no longer point to the orphaned widget. |
I agree. The concern is we have to make sure if you have permission to delete widgets, which most roles do, that you can't delete widgets used by dashboards of other users, as the new behavior would mean you are modifying other user's dashboards. For example, if I'm a basic user, I shouldn't be able to delete widgets used in dashboards for administrators or other higher privilege users. It might be something only a super administrator can do. I'll have to think about it. |
Yes, the ability to delete widgets should be restricted to super administrators. I think it would be beneficial to include an option that allows the deletion privilege to be enabled or disabled when copying this role to create other roles. |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on |
When I create a group dashboard and add widgets, and when users from that group access the dashboard, it automatically creates a user-specific dashboard by duplicating the group dashboard for each user in the database. When widgets are removed from the group dashboard and when I try to delete the widget an error occurs stating that the widget is present in user-specific dashboards and cannot be deleted. However, when the specific user checks their dashboard, the widget is not present.
ManageIQ-Verison: 4.2.0
Error:
We are running this query to view the complete error:
The text was updated successfully, but these errors were encountered: