You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: NA. not a regression but a continued fix
[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: NA
[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 Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Create a new account.
Reload the app with this account.
Log out of the app (close it completely).
There should be no navigation-related errors appearing in the console.
@VictoriaExpensify Added the checklist as well. Could you kindly add the payment summary. The fix is in production for more than 7 days and has no regression.
Activity
melvin-bot commentedon Oct 20, 2025
Triggered auto assignment to @VictoriaExpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.VictoriaExpensify commentedon Oct 21, 2025
Hey @pecanoro is this just standard payment of $250?
pecanoro commentedon Oct 21, 2025
@VictoriaExpensify I don't remember what the guidelines say. In this case, it was only a PR review and there was no proposal stage for the issue.
abdulrahuman5196 commentedon Oct 27, 2025
@pecanoro I think usually its the same contribution as a standard issue. Correct me if wrong anyways.
For example, this issue also same case - 70315, with standard payment.
abdulrahuman5196 commentedon Oct 27, 2025
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: NA. not a regression but a continued fix
[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: NA
[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 Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
abdulrahuman5196 commentedon Oct 27, 2025
@VictoriaExpensify Added the checklist as well. Could you kindly add the payment summary. The fix is in production for more than 7 days and has no regression.
VictoriaExpensify commentedon Oct 28, 2025
Payment summary:
C+: @abdulrahuman5196 owed $250 via NewDot
Thanks @abdulrahuman5196 !
trjExpensify commentedon Oct 31, 2025
approved $250 for @abdulrahuman5196