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
In the Audit context, the name “Control” defines a process created to mitigate a risk found in the company. I have many customers asking me to change the “Controls” bar name, because it is misleading to them.
Proposed Solution
Create an "settings/3dots button" on the right side of the opened "Controls" menu. Inside it, an option to change the "Controls" label. Or maybe, we could be able to change the name double clicking the label.
Other Information
No response
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
CLI version used
v2
Environment details (OS name and version, etc.)
Windows 11 v23H2
The text was updated successfully, but these errors were encountered:
Hi @dkabal14, thanks for reaching out. This repository tracks issues for specifically the AWS CLI. A feature request about QuickSight's UI would have be directed to the QuickSight service team. Opening a feature request in QuickSight Community is probably your best path forward.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Describe the feature
Can we have an option to change the "Controls" label on the top-left of the dashboard?
Use Case
Based on this Quicksight community post.
In the Audit context, the name “Control” defines a process created to mitigate a risk found in the company. I have many customers asking me to change the “Controls” bar name, because it is misleading to them.
Proposed Solution
Create an "settings/3dots button" on the right side of the opened "Controls" menu. Inside it, an option to change the "Controls" label. Or maybe, we could be able to change the name double clicking the label.
Other Information
No response
Acknowledgements
CLI version used
v2
Environment details (OS name and version, etc.)
Windows 11 v23H2
The text was updated successfully, but these errors were encountered: