Hi,
I am currently working with DPR 2.0.0 and I've been reviewing how the approvals and, more importantly, the rejection process works within the DPR Task. I have documented the current behavior and wanted to inquire if the DPR Product team has plans to address this.
Here is the current behavior I've observed: When a release is created and started, an approval task is assigned to Group A (based on my release template), which consists of four members. Approval is requested, and at this point, the state of approval for each of the four members shows as "requested." If Member 1 rejects the task, the status against their name changes to "rejected," but for the remaining three members, the status remains "requested." When Member 3 (or any of Members 2 or 4) approves the task, the task is closed.
In my opinion, the expected behavior should be as follows: Once Member 1 rejects the task, the system should ideally update the status to "no longer required" for the other members. The only way to move it back to "requested" or re-initiate approval is by clicking the "re-request approval" button.
I would appreciate it if you could provide clarification on two points:
1. What is the rationale behind designing the system in its current way, where approvals are still sought from other members despite one member rejecting the task Please note that I've set my approvals (approval definitions) to Wait for "First Response" and not All responses or percentage.
2. What are your thoughts on my proposed expected behavior?
Thank you for your time and attention. I look forward to your response.
