You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's common that users copy each other's dashboards to get started or make minor changes that meet their own requirements. Not being able to use Save as dashboard as a viewer is a big limitation for some organizations.
When users load a dashboard the backend should query the database and see if the user is editor in any folders. If that the case, Grafana should enable the user to use Save As and give the user a modal asking for which folder the dashboard should be saved in.
The text was updated successfully, but these errors were encountered:
marefr
changed the title
[Feat] Should be able to use "Save As" as a viewer
[Feat] Should enable "Save As" as when viewers_can_edit are enabled
Apr 25, 2018
torkelo
changed the title
[Feat] Should enable "Save As" as when viewers_can_edit are enabled
[Feat] Should enable "Save As" when a user with viewer role has edit permission in another folder
Apr 25, 2018
* grafana/master:
Revert "Opportunities to unindent code (unindent)"
changelog: add notes about closing grafana#11625
remove jest it.only to not skip important tests
--amend
fix: improved handling of http server shutdown
dashboard: show save as button if can edit and has edit permission to folders
new property for current user indicating if edit permissions in folders
Use opportunities to unindent code (unindent)
It's common that users copy each other's dashboards to get started or make minor changes that meet their own requirements. Not being able to use
Save as
dashboard as a viewer is a big limitation for some organizations.When users load a dashboard the backend should query the database and see if the user is editor in any folders. If that the case, Grafana should enable the user to use
Save As
and give the user a modal asking for which folder the dashboard should be saved in.The text was updated successfully, but these errors were encountered: