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 footer buttons in the "Enroll managed application" UI for assigning a Disaster Recovery (DR) policy to an application are not aligned with the PatternFly guidelines. Currently, the buttons are arranged as "Next," "Back," and "Cancel." According to PatternFly, the recommended button order should be "Back," "Next," and "Cancel."
Steps to Reproduce:
Open the "Enroll managed application" UI for assigning a DR policy.
Observe the button order in the footer of the screen.
Expected Result: The buttons should appear in the order:
Back, Next, Cancel
Actual Result: The buttons currently appear in the order:
Next, Back, Cancel
Proposed Solution: Update the button order in the footer to match the PatternFly standard:
Place "Back" as the first button.
Place "Next" as the second button.
Place "Cancel" as the third button.
The text was updated successfully, but these errors were encountered:
This need to be handled in two places
The footer buttons in the "Enroll managed application" UI for assigning a Disaster Recovery (DR) policy to an application are not aligned with the PatternFly guidelines. Currently, the buttons are arranged as "Next," "Back," and "Cancel." According to PatternFly, the recommended button order should be "Back," "Next," and "Cancel."
Steps to Reproduce:
Open the "Enroll managed application" UI for assigning a DR policy.
Observe the button order in the footer of the screen.
Expected Result: The buttons should appear in the order:
Back, Next, Cancel
Actual Result: The buttons currently appear in the order:
Next, Back, Cancel
Proposed Solution: Update the button order in the footer to match the PatternFly standard:
Place "Back" as the first button.
Place "Next" as the second button.
Place "Cancel" as the third button.
The text was updated successfully, but these errors were encountered: