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
When a user attempts to create a component using the clone strategy and opts to use repository credentials by checking the "repository credentials" checkbox, the system correctly displays a warning message if the repository login or password input fields are left empty. However, the issue arises as the user can still proceed to create the component despite the warning, which should not be permissible.
Steps to Reproduce:
Navigate to the component creation page.
Select the clone strategy for component creation.
Activate the "repository credentials" checkbox.
Leave the repository login and/or password input fields empty.
Observe the warning message but proceed to create the component.
Expected Result:
The system should prevent the user from creating the component when the repository credentials are incomplete or not provided, even if the "repository credentials" checkbox is active.
Actual Result:
The user is able to create the component with incomplete repository credentials despite the warning message.
The text was updated successfully, but these errors were encountered:
When a user attempts to create a component using the clone strategy and opts to use repository credentials by checking the "repository credentials" checkbox, the system correctly displays a warning message if the repository login or password input fields are left empty. However, the issue arises as the user can still proceed to create the component despite the warning, which should not be permissible.
Steps to Reproduce:
Expected Result:
The system should prevent the user from creating the component when the repository credentials are incomplete or not provided, even if the "repository credentials" checkbox is active.
Actual Result:
The user is able to create the component with incomplete repository credentials despite the warning message.
The text was updated successfully, but these errors were encountered: