Skip to content

fix: Display correct participant answer from alert (M2-10904) - #2245

Open
divbzero wants to merge 4 commits into
developfrom
M2-10904-display-correct-participant-answer
Open

fix: Display correct participant answer from alert (M2-10904)#2245
divbzero wants to merge 4 commits into
developfrom
M2-10904-display-correct-participant-answer

Conversation

@divbzero

Copy link
Copy Markdown
Contributor
  • Tests for the changes have been added

📝 Description

🔗 Jira Ticket M2-10904

Changes include:

  • Pass selectedDate and answerId as query params when navigating from alert
  • Reselect answer from the route when different answer is already selected
  • Remount responses when the participant or activity changes

🪤 Peer Testing

Given an activity with responses from two participants:

  1. Open panel to see alerts.

  2. Click Participant 1 alert → Take me to the response data.

    Expected outcome: Participant 1 responses are displayed.

  3. Open the right panel to see alerts.

  4. Click the Participant 2 alert → Take me to the response data.

    Expected outcome: Participant 2 responses are displayed.

The correct participant answer should be displayed even if two participants answered on the same date.

divbzero added 3 commits July 29, 2026 11:02
The previous guard skipped selection whenever an answer was already
selected. The updated guard reselects when answerId/submitId changes.
Previously, the review screen kept its state across participants and did
not refresh if the date remained unchanged. Now, the review screen
refreshes on subjectId + (activityId | activityFlowId).
@aws-amplify-us-east-1

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2245.d2ccder08v9rmu.amplifyapp.com

@sricharan-varanasi sricharan-varanasi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Chris

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants