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
[Pay 4/29][$250] [Track Tax] Error on Amount and Merchant field after changing tax rate when scanning is ongoing #39699
👋 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.
@adelekennedy 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.
@adelekennedy , thanks for double checking. This was an edge case (and/or a mistake on my part), I've paid @cubuspl42 for this outside of this issue. I checked to box above,
Activity
melvin-bot commentedon Apr 5, 2024
Triggered auto assignment to @lakchote (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 5, 2024
Triggered auto assignment to @adelekennedy (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.github-actions commentedon Apr 5, 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:
izarutskaya commentedon Apr 5, 2024
@adelekennedy 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.
izarutskaya commentedon Apr 5, 2024
We think this issue might be related to the #collect project.
55 remaining items
mallenexpensify commentedon May 1, 2024
@adelekennedy , thanks for double checking. This was an edge case (and/or a mistake on my part), I've paid @cubuspl42 for this outside of this issue. I checked to box above,
@lakchote , @adelekennedy @tienifr do we want a regression test for this?
melvin-bot commentedon May 3, 2024
@lakchote @adelekennedy @tienifr this issue is now 4 weeks old, please consider:
Thanks!
lakchote commentedon May 6, 2024
I think a regression test can't hurt to prevent this from happening in the future and ensuring a smooth user experience.
adelekennedy commentedon May 6, 2024
Then to close this out @tienifr will you suggest a regression test and I can create an issue for it?
mvtglobally commentedon May 6, 2024
Issue not reproducible during KI retests. (First week)
adelekennedy commentedon May 8, 2024
bump @tienifr for the test steps!