Skip to content
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-02-09] [HIGH] Ensure the expense is added to report from which it was requested from #34906

Closed
mountiny opened this issue Jan 22, 2024 · 20 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Internal Requires API changes or must be handled by Expensify staff NewFeature Something to build that is a new item.

Comments

@mountiny
Copy link
Contributor

mountiny commented Jan 22, 2024

### Problem

Users can go to expense report detail and request money from within that expense report. The correct money request reportID is passed to the backend but its never used actually. We do get the linked money request report as any other time which isn't guaranteed to be the same as we can have multiple open or processing reports

FYI this is being discussed in this internal slack thread

Solution

Make sure to use the provided money request report when provided in the createIOUTransaction call.

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~016be31384661b2a09
  • Upwork Job ID: 1749503890650640384
  • Last Price Increase: 2024-01-22
Issue OwnerCurrent Issue Owner: @muttmuure
@mountiny mountiny added Daily KSv2 Internal Requires API changes or must be handled by Expensify staff NewFeature Something to build that is a new item. labels Jan 22, 2024
@mountiny mountiny self-assigned this Jan 22, 2024
Copy link

melvin-bot bot commented Jan 22, 2024

Job added to Upwork: https://www.upwork.com/jobs/~016be31384661b2a09

Copy link

melvin-bot bot commented Jan 22, 2024

Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak (Internal)

@mountiny
Copy link
Contributor Author

Auth change is ready to be reviewed and merged, tests are passing, but I have found out there must have been some changes in the App and we are not necessarily sending the reportID of a report from which we have requested the money from

I will have to handle those changes too

@mountiny
Copy link
Contributor Author

Still need to complete the App PR, will focus on that tomorrow

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Jan 26, 2024
@mountiny
Copy link
Contributor Author

PR is in review, addressed initial round of feedback

@greg-schroeder greg-schroeder changed the title [Wave6] Ensure the expense is added to report from which it was requested from [HIGH] Ensure the expense is added to report from which it was requested from Jan 31, 2024
@Expensify Expensify deleted a comment from melvin-bot bot Feb 1, 2024
@mountiny mountiny added NewFeature Something to build that is a new item. and removed NewFeature Something to build that is a new item. labels Feb 2, 2024
Copy link

melvin-bot bot commented Feb 2, 2024

@mountiny
Copy link
Contributor Author

mountiny commented Feb 2, 2024

This is done basically

$500 to @eVoloshchak for review and testing please

@mountiny
Copy link
Contributor Author

mountiny commented Feb 2, 2024

@eVoloshchak could you please propose a testRail case for this? specifically on Collect policy with bunch of Open reports to the testers can verify the expense is correctly added to that expense report

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Feb 2, 2024
@melvin-bot melvin-bot bot changed the title [HIGH] Ensure the expense is added to report from which it was requested from [HOLD for payment 2024-02-09] [HIGH] Ensure the expense is added to report from which it was requested from Feb 2, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Feb 2, 2024
Copy link

melvin-bot bot commented Feb 2, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Feb 2, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.35-7 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-02-09. 🎊

For reference, here are some details about the assignees on this issue:

  • @eVoloshchak requires payment through NewDot Manual Requests

Copy link

melvin-bot bot commented Feb 2, 2024

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • [@eVoloshchak] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
  • [@muttmuure] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

https://github.com/Expensify/Expensify/issues/370624

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Feb 9, 2024
Copy link

melvin-bot bot commented Feb 9, 2024

Payment Summary

Upwork Job

BugZero Checklist (@muttmuure)

  • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
  • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1749503890650640384/hired)
  • I have paid out the Upwork contracts or cancelled the ones that are incorrect
  • I have verified the payment summary above is correct

@muttmuure
Copy link
Contributor

$500 - @eVoloshchak

@melvin-bot melvin-bot bot added the Overdue label Feb 12, 2024
Copy link

melvin-bot bot commented Feb 13, 2024

@eVoloshchak, @mountiny, @muttmuure Whoops! This issue is 2 days overdue. Let's get this updated quick!

@muttmuure
Copy link
Contributor

@eVoloshchak please can you submit a regression test

@melvin-bot melvin-bot bot removed the Overdue label Feb 13, 2024
@eVoloshchak
Copy link
Contributor

Regression Test Proposal

Preconditions:

  • Have a Collect policy set up to work with NewDot
  • Employee is a member of said policy

Test steps:

  1. As the Employee, go to OldDot and create a New Report
  2. Create multiple empty draft/open reports
  3. Go to any of those expense reports
  4. From the Composer + button, request money -> Manual
  5. Verify that the request was added to the particular report you've requested it from
  6. Repeat steps 3-5 for Scan and Distance

Do we agree 👍 or 👎

@JmillsExpensify
Copy link

$500 approved for @eVoloshchak based on this comment.

@melvin-bot melvin-bot bot added the Overdue label Feb 15, 2024
@mountiny
Copy link
Contributor Author

Lets add this regression test and we can close this

Copy link

melvin-bot bot commented Feb 19, 2024

@eVoloshchak, @mountiny, @muttmuure Eep! 4 days overdue now. Issues have feelings too...

@muttmuure
Copy link
Contributor

Created

@melvin-bot melvin-bot bot removed the Overdue label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Internal Requires API changes or must be handled by Expensify staff NewFeature Something to build that is a new item.
Projects
No open projects
Development

No branches or pull requests

4 participants