-
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
[HOLD for payment 2024-12-20] [$250] Expense shared with accountant shows incorrect rate #46897
Comments
Triggered auto assignment to @sonialiap ( |
Job added to Upwork: https://www.upwork.com/jobs/~019b051306a76e7ed6 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Pujan92 ( |
@Pujan92, @sonialiap Huh... This is 4 days overdue. Who can take care of this? |
How can we enable the rate option for personal track expense? I think distance rate feature only available in workspace |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@Pujan92, @sonialiap Still overdue 6 days?! Let's take care of this! |
@wildan-m I believe you're correct that you can't change the rate on a personal expense, but you don't need to do that. For this issue you want to have a workspace with multiple rates. Then, once you share the expense with someone on that workspace you will have the option to select one of the workspace rates |
I'm OOO Aug 19-30, adding leave buddy Status: Status: waiting for/ c+ reviewing proposals |
Triggered auto assignment to @mallenexpensify ( |
I would suggest holding this issue for #47136 - I’m planning to address a couple of Rate-related issues in it holistically. Currently we are discussing potential BE changes that will help eliminate multiple existing bugs easier. |
@Pujan92, @sonialiap, @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@Pujan92 @sonialiap @mallenexpensify 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! |
@NickTooker may we please have a copy check based on this comment? |
@neil-marcellini and I discussed the copy in Slack. We've agreed on the final version of the below:
|
Add me back to this issue if/when I am needed please. |
Does the 'm' in moved above need to be capitalized? |
@paultsimura, @Pujan92, @sonialiap, @mallenexpensify, @neil-marcellini Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not overdue, adding to the PR today. |
@paultsimura, @Pujan92, @sonialiap, @mallenexpensify, @neil-marcellini Eep! 4 days overdue now. Issues have feelings too... |
The PR is ready for review. cc: @Pujan92 |
@paultsimura, @Pujan92, @sonialiap, @mallenexpensify, @neil-marcellini Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
@paultsimura, @Pujan92, @sonialiap, @mallenexpensify, @neil-marcellini 10 days overdue. Is anyone even seeing these? Hello? |
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. |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.75-6 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-12-20. 🎊 For reference, here are some details about the assignees on this issue:
|
@paultsimura / @Pujan92 @sonialiap / @mallenexpensify @paultsimura / @Pujan92 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
hmm... wonder why @paultsimura is mentioned twice above. Going to :donothing: since I've yet to see this before |
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: 9.0.17-0
Reproducible in staging?: y
Reproducible in production?: y
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: @paultsimura
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722892285723489
Action Performed:
Expected Result:
Actual Result:
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
354815793-ed56f179-938c-4d0c-9569-4416a6093059.mp4
Recording.415.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @sonialiap / @mallenexpensifyThe text was updated successfully, but these errors were encountered: