-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-10-14] [$250] Categories - RBR appears next to workspace after selecting the deleted spend category offline #49295
Comments
Triggered auto assignment to @RachCHopkins ( |
@RachCHopkins 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 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Categories - RBR appears next to workspace after selecting the deleted spend category offline. What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?We should check the current category and the selected category and if they are the same then we shouldn't call const setNewCategory = (selectedCategory: ListItem) => {
if (!selectedCategory.keyForList || selectedCategory.keyForList===categoryID) {
return;
}
Policy.setWorkspaceDefaultSpendCategory(policyID, groupID, selectedCategory.keyForList);
}; What alternative solutions did you explore? (Optional)Result |
Ok, so we are saying that if you set an MCC default, then delete the category you set, it shows as Uncategorised and has a red dot with no error message. I would think that if we think that people will be deleting their categories offline, and causing the MCC default to break, the solution would be displaying an error of some variety. I don't think this is a "real" problem that users will encounter, but hey, let's pretend they are working from somewhere with dodgy reception and they happen to be doing major surgery on their categories, then it should behave the same as it would if they were online. Unfortunately I can't seem to work out what that is. @IuliiaHerets how are you seeing the MCC defaults? Is there a prerequisite that's not on the OP there? I can't see this on Collect or Control. |
Asked in Slack. |
@RachCHopkins, the RBR occurs only if we selected the deleted category again, the RBR does not occur on initial deletion of the category. |
@RachCHopkins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Ok, I still can't replicate this. I'm going to have to assume that it's ok. |
Job added to Upwork: https://www.upwork.com/jobs/~021838337226742068992 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
@Krishna2323 Thanks for the proposal. The RCA and the solution makes sense to me. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @NikkiWines, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Agreed, @Krishna2323's proposal looks good 👍 |
📣 @Krishna2323 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@s77rt, PR ready for review. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.45-4 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-10-14. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
|
Payment Summary:
Upwork job here |
Contributor has been paid, the contract has been completed, and the Upwork post has been closed. |
$250 approved for @s77rt |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.35-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): applausetester+kh010901@applause.expensifail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
There will not be RBR next to the workspace.
Actual Result:
RBR appears next to the workspace after selecting the deleted spend category offline, but there is no error message anywhere.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6604548_1726420009054.20240916_010231.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @RachCHopkinsThe text was updated successfully, but these errors were encountered: