-
Story
-
Resolution: Done
-
Critical
-
None
-
Product / Portfolio Work
-
5
-
False
-
-
False
-
-
Green
-
agreed on including it for 2.16
-
-
-
ACM Console Train 36 - 2
-
None
the design is representing the new scope selection flow approach, meaning
A. Global access to everything in the ACM
If selecting cluster sets
B. Everything in the selected cluster sets
C. Specific common projects on all clusters in the set
If selecting clusters
D. Everything in the selected clusters
F. Specific common projects on the clusters
it will require: * Wizard to adapt steps
- Access level step to adapt the dropdown and add the alert
- Cluster granularity step to adapt the dropdown and add the alert
- To adapt the onSubmit call and maybe review step
- I would additionally add a progress bar on the create common project form, due to it could mean to perform dozens of requests
check conversation at https://redhat-internal.slack.com/archives/C049M2XDJBZ/p1769421547685009
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](
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.