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-04-05] [Simplified Collect][Distance rates] - Error shows up when disabling and renaming distance rate #38815
Version Number: 1.4.56-0 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
User is admin of Collect workspace
Go to staging.new.expensify.com
Go to Profile > Workspaces > Collect workspace
Go to Distance rates
Add a distance rate
Click on the distance rate added in Step 4
Toggle off the Enable rate button
Click Rate and edit the rate
Expected Result:
App will save the new settings made in Step 6 and 7
Actual Result:
Error shows up when disabling and renaming distance rate
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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.
@stitesExpensify 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
changed the title [-]Distance rates - Error shows up when disabling and renaming distance rate[/-][+][Simplified Collect][Distance rates] - Error shows up when disabling and renaming distance rate[/+]on Mar 22, 2024
changed the title [-][Simplified Collect][Distance rates] - Error shows up when disabling and renaming distance rate[/-][+][HOLD for payment 2024-04-05] [Simplified Collect][Distance rates] - Error shows up when disabling and renaming distance rate[/+]on Mar 29, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.57-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Activity
github-actions commentedon Mar 22, 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 Mar 22, 2024
Triggered auto assignment to @stitesExpensify (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.lanitochka17 commentedon Mar 22, 2024
We think that this bug might be related to #wave-control
lanitochka17 commentedon Mar 22, 2024
@stitesExpensify 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
[-]Distance rates - Error shows up when disabling and renaming distance rate[/-][+][Simplified Collect][Distance rates] - Error shows up when disabling and renaming distance rate[/+]luacmartins commentedon Mar 22, 2024
This is not a blocker since this feature is not available to users yet.
luacmartins commentedon Mar 22, 2024
cc @MrMuzyk
3 remaining items
luacmartins commentedon Mar 22, 2024
This is the error that I get. This was already fixed here

[-][Simplified Collect][Distance rates] - Error shows up when disabling and renaming distance rate[/-][+][HOLD for payment 2024-04-05] [Simplified Collect][Distance rates] - Error shows up when disabling and renaming distance rate[/+]melvin-bot commentedon Mar 29, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 29, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.57-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-04-05. 🎊
melvin-bot commentedon Apr 5, 2024
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
luacmartins commentedon Apr 5, 2024
This is done