-
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
[$250] Invoice - No option 'Pay via Expensify' for receiver #48486
Comments
Triggered auto assignment to @twisterdotcom ( |
@user Your proposal will be dismissed because you did not follow the proposal template. |
ProposalPlease re-state the problem that we are trying to solve in this issue.No option 'Pay via Expensify' for receiver What is the root cause of that problem?We are not pushing pay with expensify option in button options App/src/components/SettlementButton.tsx Lines 215 to 260 in 0139133
What changes do you think we should make in order to solve the problem?We can push pay with expensify option
What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.Invoice - No option 'Pay via Expensify' for receiver What is the root cause of that problem?The Hence the App/src/components/SettlementButton.tsx Lines 223 to 239 in 0139133
This also happens in the dropdown for business. App/src/components/SettlementButton.tsx Lines 242 to 253 in 0139133
What changes do you think we should make in order to solve the problem?We should add the settle with Expensify option in the While checking for
Or we can push the settle with Expensify option in the |
Edited by proposal-police: This proposal was edited at 2023-10-02T00:00:00Z. ProposalPlease re-state the problem that we are trying to solve in this issue.No Pay via Expensify option for invoice What is the root cause of that problem?The cause is separate for main and staging, In staging (9.0.28-1): App/src/components/SettlementButton.tsx Line 198 in a124e4f
App/src/components/SettlementButton.tsx Lines 209 to 211 in a124e4f
The check for What changes do you think we should make in order to solve the problem?Add back the changes to bring back the button. Mainly, we need to add back the value in paymentMethod object and the code to push it in buttonOptions. Then remove If the invoice report needs to be part of What alternative solutions did you explore? (Optional) |
Updated proposal
|
Job added to Upwork: https://www.upwork.com/jobs/~015c21e7f83c78f5bb |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani ( |
Hmm... actually... I wonder if these expected result steps are wrong:
@davidcardoza is this right now? I feel like this makes more sense. |
Users can't pay an invoice via Expensify just yet. The options should be
Regardless of the selection "Pay elsewhere" should be the only option. We're prioritizing invoice payments as part of the VIP-Bill-pay project. @madmax330 |
Okay, I think this is just a bug with an ongoing project right? I don't think we need to open this up to contributors right now. |
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.28-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: https://expensify.testrail.io/index.php?/cases/view/3073288
Issue reported by: Applause - Internal Team
Action Performed:
Precondition: workspace with a member added
Expected Result:
There are options 'Pay elsewhere' and 'Pay via Expensify' in a button dropdown
Actual Result:
There are options 'Pay as business' and 'Pay as an individual' in a button dropdown. No 'Pay via Expensify'
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6591768_1725371898335.pay_invoice.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jayeshmangwaniThe text was updated successfully, but these errors were encountered: