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
Scan- Wrong IOU details in the notification email #37518
Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: Applause internal team Slack conversation:
Action Performed:
1.Log in in the app
2.Request money to an account that you have access to the email inbox
3.Do not read the message in NewDot to trigger the email notification
Expected Result:
IOU email subject and body display requestee requested amount
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
@rlinoz FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
@m-natarajan can you clarify which account's email you're checking? Also what your account relationships are like. The accounts I tested with both own workspaces that the other is a part of. Account A has issued multiple requests (testing), should there be a clean slate - no outstanding expenses?
Activity
melvin-bot commentedon Feb 29, 2024
Triggered auto assignment to @sonialiap (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.github-actions commentedon Feb 29, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Feb 29, 2024
Triggered auto assignment to @rlinoz (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.m-natarajan commentedon Feb 29, 2024
@rlinoz FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
sonialiap commentedon Feb 29, 2024
@m-natarajan can you clarify which account's email you're checking? Also what your account relationships are like. The accounts I tested with both own workspaces that the other is a part of. Account A has issued multiple requests (testing), should there be a clean slate - no outstanding expenses?
I tried
puneetlath commentedon Feb 29, 2024
This is a back-end issue, so going to remove the DeployBlockerCash label.
rlinoz commentedon Mar 4, 2024
Related to #35353, will take a look later.
rlinoz commentedon Mar 6, 2024
Done with the other issue, going to take a look at this tomorrow.
rlinoz commentedon Mar 14, 2024
The fix is in prod https://github.com/Expensify/Web-Expensify/pull/41179#issuecomment-1994978426, closing this one.