-
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-07-23][$250] We're requiring merchants when sending an invoice, when we shouldn't be. #44126
Comments
ProposalPlease re-state the problem that we are trying to solve in this issue.Merchant is required for invoice request even though it shouldn't. What is the root cause of that problem?This happens after this PR where we change it so the merchant is required when creating or editing the invoice.
Previously, the invoice was only required in edit invoice detail, but the PR above makes it consistent so creating an invoice also requires a merchant. What changes do you think we should make in order to solve the problem?Because we do not want to make it required, we need to "revert" that PR. We will remove the invoice type condition from both of these codes
To fix it, we have 2 options:
|
Damn, it looks like the other PR linked was created to make it so that a merchant name is required on invoices. Unfortunately the invoicing project team didn't catch it because it never passed through the project Slack channel or the project board. That proposal looks good @bernhardoj |
Job added to Upwork: https://www.upwork.com/jobs/~010f4b3b019ed717d4 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rayane-djouah ( |
Triggered auto assignment to @miljakljajic ( |
@bernhardoj's proposal looks good to me 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @techievivek, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@miljakljajic, @techievivek, @rayane-djouah Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@techievivek - Friendly bump ^^ |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
No update on this, until @techievivek comes back |
@miljakljajic, @techievivek, @rayane-djouah Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@miljakljajic - Can we assign another CME as @techievivek is OOO? |
📣 @rayane-djouah 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR is ready cc: @rayane-djouah |
What will the payment date for this one be? |
It's deployed to prod 3 days ago, so it should be 23 July |
Not overdue |
Both contributors paid! |
If you go to Send Invoice, and then input a user, we're requiring a merchant name. We should not be requiring the merchant. This is reproducable on all platforms for me.
cc @davidcardoza @cristipaval
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @miljakljajicThe text was updated successfully, but these errors were encountered: