Story (Required)

• When approvals/rejections are submitted:

• • Group members must have their responses reflected in both the group input and the detailed status.approverResponse.

• • Individual users should follow the existing approval flow while ensuring group membership is considered.

• Responses must be logged accurately for auditability and counted toward overall approval decisions.

• The implementation should include unit tests, end-to-end tests, and internationalization (I18n) support.

Acceptance Criteria (Mandatory)

• Patch Operations for Individual and Group Users on Approval Tasks
• When a group user approves/rejects:
• Update the group member message if provided by the user.
• Update the group input.
• Update the user list with the provided input and message.
• Update the group members within the status.approverResponse.

• When an individual user approves/rejects:
• Verify if the user is a member of a group; if not, adhere to the existing approval process.

• User approval responses should be counted.
• Unit tests for this functionality are required.
• End-to-end (e2e) tests for this functionality are required.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met