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
The task involves enhancing the existing Resource Quota (RQ) widget to include additional namespace metrics derived from the kind: Tenant status for the Deployment Flows section. This enhancement aims to provide users with a more comprehensive view of their resource allocations and usages. Additionally, the task includes the integration of user-friendly messages for each of the metrics and widget names to improve the overall user experience and understanding of the displayed data.\n\nh4. Acceptance Criteria\n1. Namespace metrics are successfully integrated into the RQ widget.\n2. User-friendly messages are developed and displayed for each metric and widget name.\n3. The enhanced RQ widget is tested to ensure accuracy and usability.\n4. Documentation is updated to reflect the new widget features and to guide users on how to interpret the new metrics.
--
Recently, it has become apparent that determining the correct default namespace for users of the Portal UI can be challenging. To address this issue, we propose the introduction of a new attribute named 'namespace' within Keycloak. This attribute should be included as part of the JWT user token. Upon receiving the token, the Portal UI will check for this 'namespace' value and utilize it to establish the default_namespace for the user session. In instances where the JWT token lacks the 'namespace' attribute, the Portal UI will revert to its existing method for default namespace determination.
Acceptance Criteria
A new attribute named 'namespace' is created within Keycloak.
The 'namespace' attribute is included as part of the JWT user token.
The Portal UI is updated to check the JWT token for the 'namespace' attribute.
If the 'namespace' attribute is present, the Portal UI uses this value to set the default_namespace.
If the 'namespace' attribute is absent, the Portal UI defaults to its current behavior for determining the default namespace.
--
The User Info section of the UI currently lacks personalization options for displaying user-specific information. To enhance user experience and make the interface more engaging, it is proposed to include a feature to display the user avatar next to the user's information in the User Info section.
Acceptance Criteria
A user avatar is displayed next to the user's name in the User Info section.
The avatar should be dynamically loaded based on the user's profile picture.
If the user does not have a profile picture set, a default avatar image should be displayed.
The user avatar should be circular and have a diameter of 40 pixels.
The avatar should be aligned in such a way that it maintains consistent spacing with the user's name and other elements in the User Info section.
Ensure that the feature is responsive and the avatar's visibility and alignment are maintained across different screen sizes.
The text was updated successfully, but these errors were encountered:
The task involves enhancing the existing Resource Quota (RQ) widget to include additional namespace metrics derived from the
kind: Tenant
status for the Deployment Flows section. This enhancement aims to provide users with a more comprehensive view of their resource allocations and usages. Additionally, the task includes the integration of user-friendly messages for each of the metrics and widget names to improve the overall user experience and understanding of the displayed data.\n\nh4. Acceptance Criteria\n1. Namespace metrics are successfully integrated into the RQ widget.\n2. User-friendly messages are developed and displayed for each metric and widget name.\n3. The enhanced RQ widget is tested to ensure accuracy and usability.\n4. Documentation is updated to reflect the new widget features and to guide users on how to interpret the new metrics.--
Recently, it has become apparent that determining the correct default namespace for users of the Portal UI can be challenging. To address this issue, we propose the introduction of a new attribute named 'namespace' within Keycloak. This attribute should be included as part of the JWT user token. Upon receiving the token, the Portal UI will check for this 'namespace' value and utilize it to establish the default_namespace for the user session. In instances where the JWT token lacks the 'namespace' attribute, the Portal UI will revert to its existing method for default namespace determination.
Acceptance Criteria
A new attribute named 'namespace' is created within Keycloak.
The 'namespace' attribute is included as part of the JWT user token.
The Portal UI is updated to check the JWT token for the 'namespace' attribute.
If the 'namespace' attribute is present, the Portal UI uses this value to set the default_namespace.
If the 'namespace' attribute is absent, the Portal UI defaults to its current behavior for determining the default namespace.
--
The User Info section of the UI currently lacks personalization options for displaying user-specific information. To enhance user experience and make the interface more engaging, it is proposed to include a feature to display the user avatar next to the user's information in the User Info section.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: