when configuring gatekeeping rules, we can only enter users and not teams/groups

To add to that, one more requirement that we need to make sure UCV can meet (unless there is a way for us to write a script to call):

• For each "Gate" - we need to enforce separation of duties, meaning the same person cannot approve more than one rule in the same Gate. For example (using the example below) - if Bob already approved the Production Gate manual rule for the Test Architect, Bob cannot approve the Production Gate manual rule for the Release Coordinator. It is possible that Bob is in multiple AD groups (we have this today).

Feel free to recommend other ways we can use UCV to accomplish our story. Also - not that it matters, but I listed the approvals in the wrong order - it's (1) Test Architect (2) Executive Sponsor and (3) Release Coordinator

Clarifying requirements:

• A Gate needs to have multiple manual rules used as our approvals

• Order matters! Each manual rule (approval) needs to occur in a specific order, for example for Production:

  • Approval 1 = Test Architect AD Group

  • Approval 2 = Release Coordinator AD Group

  • Approval 3 = Executive Sponsor AD Group

• Manual rules need to be assigned to an AD group.

• If any member of the AD group approves, then the rule/approval is passed, it shouldn't force all members of the AD group to have to approve (first one in wins)

• If any member of the AD group denies, then the deployment process is halted (does not continue to the next approval rule).

Example:

There will be a "Gate" for our Production environment (in order to capture the approvals necessary to be allowed to deploy the build to Production). The Gate will have three manual "rules" - each rule is a separate approval. The "rules" need to be in order - (first approval, second approval, third approval IN ORDER - so the second manual rule doesn't appear for approval until the first one is approved, and if the first one is denied, it gets aborted). Each rule will need to be assigned to a different AD group (e.g., manual rule 1 = Test Architect AD Group). If ANY member of the AD group assigned to that rule approves, the next manual rule is activated (only ONE member of the AD group needs to approve, not all members of the AD group).

Thank You!

it is for manual approvals. The used case(s), is to assure that management and others approve applications before pormoting for deployment to higher env

Yes please, could you describe the use case/scenario in more detail.

I was wondering also, is it for manual approvals only? Can it be solved by using the approval step in the deployment plan, or by using an automated gate?

I have updated https://cloud-platform.ideas.ibm.com/ideas/URBANCODE-I-521 to HIGH priority and put it into “In Development” state. The original prio was LOW so I did not look at it till my call with Brad last week where I changed the status to “needs information” as I wanted to check with SSA about it. Osman are you just wanting to know if this is high priority for us or do u need some more clarity on gatekeeping

The change in the state was for me internaly to clarify what is needed to proceed. Will change it to the right one

osman

do you need any further info

Thank You for the clarification

the groups that we want to assign will be AD groups