What is the impact of the issue on the customer?

The customer experiences confusion and incorrect task configuration when editing pipelines through the Pipeline Builder UI. Because the side panel displays stale or incorrect parameter data for tasks that share the same name across namespaces, users may unknowingly save or deploy pipelines with invalid configurations. This leads to potential pipeline failures and loss of confidence in the UI’s reliability.

Is there a workaround in place?

A partial workaround exists: users can manually verify and edit the pipeline YAML to ensure it references the correct task and parameters from the intended namespace. However, this requires advanced knowledge of Tekton syntax and negates the benefit of using the visual builder, making it unsuitable for most users.

OCP Version

OCP 4.16

Pipelines Operator Version

1.17, 1.18

Steps to Reproduce

1. Create a task with a name identical to an existing task in the openshift-pipelines namespace.

1. Using the Pipeline Builder UI, create a new pipeline and add the task from the openshift-pipelines namespace.

1. Observe that the Pipeline Builder side panel shows parameters from the task in the current namespace instead of the selected one.

1. Check the YAML editor — it correctly references the task from the cluster resolver and shows the accurate parameter data.

Are you able to reproduce the issue?

Yes, the issue is reproducible consistently (Always).

Name of the Customer

Jeffrey Luckett

Revenue Impact

Potential medium impact — misconfigured pipelines can lead to failed runs and delays in CI/CD workflows, increasing support overhead and decreasing user trust in the console plugin UI.

Customer Case #

Not mentioned

Reproducibility

Always

Acceptance Criteria

• The Pipeline Builder side panel should correctly display parameters from the task in the selected namespace.

• Task parameter data in the side panel must always match the source as shown in the YAML editor.

• Validation should ensure that cross-namespace task references do not display stale or incorrect data.

Definition of Done

• Code changes are implemented and merged in the console-plugin UI.

• Verified fix on both Pipelines Operator versions (1.17 and 1.18).

• Automated and manual tests confirm correct namespace resolution and data consistency between side panel and YAML view.

• Fix validated on OCP 4.16.

Build Details

Fix expected in the console-plugin repository under the Pipeline Builder component.

Additional Info

A screen recording has been shared demonstrating the issue. The side panel of the Pipeline Builder form shows stale data for tasks that share the same name across namespaces, while the YAML editor accurately reflects the task data resolved via the cluster resolver.