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
[$500] Distance - Total amount in report is not reset to 0.00 when changing distance request offline #36892
Version Number: 1.4.43-2 Reproducible in staging?: Y Reproducible in production?: N 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:
Navigate to staging.new.expensify.com
Create a new workspace (so that there is no existing request)
Go to workspace chat
Create a distance request
Go to request details page
Go offline
Click Distance
Add another stop
Return to expense report
Expected Result:
The total amount will change to 0.00 (PROD behavior)
Actual Result:
The total amount does not change to 0.00
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]Distance - Total amount in report is not reset to 0.00 when changing distance request offline[/-][+][$500] Distance - Total amount in report is not reset to 0.00 when changing distance request offline[/+]on Feb 20, 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:
Identify the pull request that introduced this issue and revert it.
Activity
[-]Distance - Total amount in report is not reset to 0.00 when changing distance request offline[/-][+][$500] Distance - Total amount in report is not reset to 0.00 when changing distance request offline[/+]melvin-bot commentedon Feb 20, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01ed2116286bd18632
melvin-bot commentedon Feb 20, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 (
External)github-actions commentedon Feb 20, 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 20, 2024
Triggered auto assignment to @madmax330 (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.lanitochka17 commentedon Feb 20, 2024
We think that this bug might be related to #wave5
CC @dylanexpensify
13 remaining items
jakub-trzebiatowski commentedon Feb 22, 2024
Thank you!
mvtglobally commentedon Mar 14, 2024
Issue not reproducible during KI retests. (First week)
ishpaul777 commentedon Mar 14, 2024
This should be ready for C+ payment @neil-marcellini Can you please remove reviewing label
melvin-bot commentedon Mar 15, 2024
Triggered auto assignment to @twisterdotcom (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Mar 15, 2024
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
twisterdotcom commentedon Mar 15, 2024
Payment Summary:
ishpaul777 commentedon Mar 15, 2024
@twisterdotcom accepted offer 🙂 Thanks!