Bug 2107469

Summary: Confusing subtitle in Create Service Binding modal when the target is already known
Product: OpenShift Container Platform Reporter: Christoph Jerolimov <cjerolim>
Component: Dev ConsoleAssignee: divgupta
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: low Docs Contact:
Priority: medium    
Version: 4.12CC: divgupta, nmukherj
Target Milestone: ---   
Target Release: 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-17 19:52:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
create-service-binding-modal-case-1.png
none
create-service-binding-modal-case-2.png none

Description Christoph Jerolimov 2022-07-15 07:22:35 UTC
Description of problem:
We've got the feedback from Rolfe from the docs-team that the subtitle in the "Create Service Binding" modal is confusing. See also https://github.com/openshift/openshift-docs/pull/47760#discussion_r921540407

The modal exists in two versions:

a) When the user creates a binding and needs to specific a target. In this case, the user needs to enter a "Name" for the SB and has the option "Bindable Service" to select a target from a dropdown.

b) When the user creates a binding and the target is already known. In this case the user can change the prefilled SB "Name". The target can not be changed and the dropdown is not shown.

The subtitle is "Select a service to connect to." in both cases. But in the second case, there is nothing to select.


Version-Release number of selected component (if applicable):
4.12, older versions as well.

How reproducible:
Always

Steps to Reproduce:
1. Install the Service Binding operator
2. Install a bindable operator, for example Crunchy Postgres or Kafka
3. Navigate to developer perspective > Add
4. Import a component from Git or Container image
5. In the topology, right-click the new Deployment and select "Create Service Binding". You can see both input fields. Cancel this!
6. Hover over the new Deployment and drag the small arrow and drop it outside of any application and choose 'Operator Backed' from the action menu.
7. Filter for 'Bindable' Service Bindings and select one.
8. Create the Bindable resource

Now you will see the topology again and the "Create Service Binding" modal without the option to select a target.

Actual results:
The modal has the same subtitle in both cases.

Case 1:
> Create Service Binding
> Select a service to connect to.
> Name *
> Bindable service *

Case 2:
> Create Service Binding
> Select a service to connect to.
> Name *

Expected results:
The modal should show another subtitle, that mentions the target resource.

For example (please check the exact sentence with PM/UX)


Case 1:
> Create Service Binding
> Select a service to connect to `$source`.    // We can show the selected resource name here as well?!
> Name *
> Bindable service *

Case 2:
> Create Service Binding
> Connect service `$target` to `$source`       // Show the created resource name here.
> Name *


We should show them maybe as a ResourceLink. In this case, we should enforce that these links are opened in a new tab so that the modal doesn't get lost?

Comment 1 Christoph Jerolimov 2022-07-15 07:23:11 UTC
*** Bug 2107470 has been marked as a duplicate of this bug. ***

Comment 2 Christoph Jerolimov 2022-07-15 07:23:48 UTC
Created attachment 1897309 [details]
create-service-binding-modal-case-1.png

Comment 3 Christoph Jerolimov 2022-07-15 07:24:02 UTC
Created attachment 1897310 [details]
create-service-binding-modal-case-2.png

Comment 5 Christoph Jerolimov 2022-08-31 09:11:55 UTC
Verified on 4.12.0-ec.2

Comment 8 errata-xmlrpc 2023-01-17 19:52:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7399