[Due for payment 2026-10-07] Payment issue for E/App PR#101664

[melvin-bot]

Issue created to compensate the Contributor+ member for their work on #101664
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/674642.
Contributor+ member who reviewed the PR - @brunovjk.

Wait 7 days after the PR is deployed to production before issuing payment in case there are regressions.

Issue Owner

Current Issue Owner: @brunovjk

[melvin-bot]

@brunovjk The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

[brunovjk]

Contributor+ Checklist:

• [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to the comment on the PR: N/A – I couldn't identify a specific offending PR. This appears to be a legacy data compatibility issue rather than a regression introduced by a single App PR.
  Link to the comment on the Issue:

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion:

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

Regression Test Proposal

Precondition:

• Use an account that has access to a legacy #admins room where the current participant has an empty notificationPreference.

Test:

1. Open the #admins room settings.
2. Verify the notification preference displays the room default instead of appearing blank or hidden.
3. Open the room Members list and verify the participant with the empty notification preference is displayed.
4. Select Daily as the notification preference and save it.
5. Reload the report and verify the notification preference remains Daily.
6. As another admin with access to the same room, verify the participant is still displayed in the Members list.

Do we agree 👍 or 👎

[brunovjk]

Contributor+ Summary

• Production: The PR went into production on Sep 30 in this deployment checklist.
• Regression: No bugs were raised regarding our PR.
• Contributor / PR Author: fedirjh
• Contributor+ Reviewer: brunovjk

Thank you.

cc: @mallenexpensify