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
This PR (#160266) fixes a bug introduced in PR- #146155.
However, the issue was not documented in the Release Notes for 8.8/8.9 as breaking changes, even though the impact is significant enough to break the view of the users as they are encountered with warning modals.
This issue prevents the users from being able to create or modify ML jobs and as some spaces have sensitive data that is not meant to be accessed by all users, and as such this change is deemed to break the user experience and would like to ask this to be documented in the release notes.
We understand that the fix is delivered in 8.10 version, so it will be helpful to include this in 8.8, 8,9 and 8.10, so users will be aware of this change and the fix versions.
The workaround without the fix is to provide access to ALL spaces, which is not ideal and fixed version would greatly improve the user experience.
Kibana version: 8.7/8.8/8.9
Any additional context:
This PR (#160266) fixes a bug introduced in PR- #146155.
However, the issue was not documented in the Release Notes for 8.8/8.9 as breaking changes, even though the impact is significant enough to break the view of the users as they are encountered with warning modals.
This issue prevents the users from being able to create or modify ML jobs and as some spaces have sensitive data that is not meant to be accessed by all users, and as such this change is deemed to break the user experience and would like to ask this to be documented in the release notes.
We understand that the fix is delivered in 8.10 version, so it will be helpful to include this in 8.8, 8,9 and 8.10, so users will be aware of this change and the fix versions.
The workaround without the fix is to provide access to ALL spaces, which is not ideal and fixed version would greatly improve the user experience.
Related PR/Issues:
capabilities.resolveCapabilities
#146881Thank you.
The text was updated successfully, but these errors were encountered: