-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Taxes - Error shows up when selecting tax rate in split scan menu #40755
Comments
Triggered auto assignment to @grgia ( |
Triggered auto assignment to @Christinadobrzyn ( |
👋 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:
|
@Christinadobrzyn 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. |
We think this issue might be related to the #collect project. |
Job added to Upwork: https://www.upwork.com/jobs/~0145ac3902090baef8 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Error "Unexpected error editing this expense, please try again later" shows up when selecting a different tax rate. What is the root cause of that problem?We're not handling the case for edit split bill tax rate in
What changes do you think we should make in order to solve the problem?Like other IOU step pages, we should subscribe
We should do the same for tax amount page. What alternative solutions did you explore? (Optional)NA |
We can demote it from a blocker as Tax for splits is WIP here Though if this is a blocker, we might have shipped some bad code related to this workflow |
Seems like we can demote based on the comment but lets make sure this is fixed fast |
This is internal issue https://expensify.slack.com/archives/C01GTK53T8Q/p1713870117792039?thread_ts=1713867930.076379&cid=C01GTK53T8Q |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
From the issue
The first part needs to be handled from backend. cc: @grgia |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@MonilBhavsar @grgia @Christinadobrzyn @c3024 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
I wonder if this should be weekly for the time being? @c3024 @MonilBhavsar @grgia what do you think? |
Those issues do not cover |
@MonilBhavsar @grgia @Christinadobrzyn @c3024 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@MonilBhavsar @c3024 @grgia can you confirm the best next step or a status for this? TY! |
#39690 does |
Thanks. Sorry for the confusion @Christinadobrzyn. This can be moved to |
monitoring - #39690 |
1 similar comment
monitoring - #39690 |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
monitoring - #39690 |
1 similar comment
monitoring - #39690 |
monitoring - #39690 Just a heads up - I'm going to be ooo until June 24th. I'm not going to assign anyone new but if you need a new BZ teammate for any reason please feel free to ask for one to be assigned here. |
This bug is fixed, we can close this issue |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.64-2
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition:
Expected Result:
User is able to select a different tax rate without issue.
Actual Result:
Error "Unexpected error editing this expense, please try again later" shows up when selecting a different tax rate.
The selected tax rate is highlighted in tax rate list, but the Tax rate row in split menu still shows the previous tax rate.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6458354_1713850176267.bandicam_2024-04-23_12-52-14-955.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: