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
{{ message }}
Repository navigation
HOLD for Payment 2024-06-21] Verification page is included in the last path visited url #43325
The PR that introduced the bug has been identified. Link to the PR: N.A. was always a problem.
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: N.A.
A discussion in #expensify-bugs 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: N.A.
Determine if we should create a regression test for this bug. Yes
If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again
1. Open the verification page - https://staging.new.expensify.com/v/123/456
2. Open the home page - https://staging.new.expensify.com
3. Verify that you aren't shown the magic code verification page
changed the title [-]Verification page is included in the last path visited url[/-][+]HOLD for Payment 2024-06-21] Verification page is included in the last path visited url[/+]on Jun 17, 2024
Activity
melvin-bot commentedon Jun 7, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (
External)melvin-bot commentedon Jun 7, 2024
Triggered auto assignment to @sakluger (
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.AndrewGable commentedon Jun 11, 2024
@adamgrzybowski - Can you comment here so I can assign you?
adamgrzybowski commentedon Jun 12, 2024
@AndrewGable 👋
rushatgabhane commentedon Jun 16, 2024
PR hit production 2 days ago - #43303 (comment)
rushatgabhane commentedon Jun 16, 2024
The PR that introduced the bug has been identified. Link to the PR: N.A. was always a problem.
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: N.A.
A discussion in #expensify-bugs 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: N.A.
Determine if we should create a regression test for this bug. Yes
If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again
rushatgabhane commentedon Jun 16, 2024
@sakluger could you please attach payment summary for the payment date - June 21
[-]Verification page is included in the last path visited url[/-][+]HOLD for Payment 2024-06-21] Verification page is included in the last path visited url[/+]sakluger commentedon Jun 17, 2024
Summarizing payment on this issue:
Contributor: @adamgrzybowski - no payment due
Contributor+: @rushatgabhane - $250 - please request on Newdot on or after June 21
sakluger commentedon Jun 17, 2024
Posted! I'm going to leave this open until the payment date.
JmillsExpensify commentedon Jun 23, 2024
$250 approved for @rushatgabhane.