one specific use case this is trying to cover * A Role Assignment is created for the cluster set cs01 and emingoraproject100 namespace. At the time RA is created cs01 contains just sno-1-vxpqx

• emingoraproject100 just exist in that particular  sno-1-vxpqx cluster
• then a new cluster  sno-1-xztwb is added to the cluster set cs01
• MulticlusterRoleAssignments CR reports an error ApplicationFailed: Failed on 1 cluster(s): RoleBinding emingoraproject100/kubevirt.io-view-028a4b740c283b80 failed on cluster }}{{{}sno-1-xztwb: Failed to apply manifest: namespaces "emingoraproject100" not found which is expected behaviour  

• Now the RA is edit, emingoraproject100 is already part of the previous RA, so it is selected in the wizard, but it doesn't appear on the project list since it is not a common project (see second attached image)

Video_2026-01-28_11-38-34.mp4

So the agreement from https://redhat-internal.slack.com/archives/C049M2XDJBZ/p1769596269216929 is a new validation mechanism on the project step not being able to proceed until the selection exists on all the cluster from the selection. Additionally to it a new button for creating the selected namespaces on the clusters from the cluster set will be exposed.

Value Statement

Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")

Definition of Done for Engineering Story Owner (Checklist)

• to adapt the RA creation wizard based on the new design
• adapt tests too

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.