-
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
[$1000] Web - Historical IOUs appearing in LHN like a pinned chat, above more recent chats, though they aren’t pinned #23438
Comments
Triggered auto assignment to @dylanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Job added to Upwork: https://www.upwork.com/jobs/~0113e10683f580c981 |
Current assignee @dylanexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ArekChr ( |
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Contributor details |
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
This is still happening to me. I had even more appear today. |
Waiting for proposals 📣 |
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
I am trying to understand exactly what is happening here. Where you perhaps waiting on a credit bank account? Lines 1071 to 1095 in 5ffd4e6
problem seems to be here in this function, either in the report.isWaitingOnBankAccount is true, or reportToLook.hasOutstandingIOU is not changed. |
@ArekChr mind giving @WikusKriek a reply? |
bump @ArekChr! |
OK, thanks for clarifying. I'm OK with this proposal now and request that the PR also:
|
📣 @mananjadhav Please request via NewDot manual requests for the Reviewer role ($1000) |
📣 @WikusKriek 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Starting on the PR now. |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
We got delayed by a few hours, I would request if we can still apply the bonus here. The QA was done, I spent quite a lot of time on getting my builds for Android and iOS. |
CC @tgolen thoughts? Seems understandable to me |
After discussing internally, we'll be sticking with the standard timeline requirement. For context, this stemmed from discussing grace periods and the outcomes where the boundaries we establish become fuzzy and ultimately hinder the initial premise behind offering this. Thanks for your understanding <3 |
Payment summary:
Upwork job. Please apply! |
Thanks for the clarification. Totally agreed. |
Waiting for regression period to be over! |
@dylanexpensify Can you please post the payment summary here? This has been in production for 7 days, but the title isn't updated. |
I couldn't pinpoint to a specific PR here, as the logic has existed since long. I also don't think we need to add a regression test here. |
@dylanexpensify Quick bump on this one. |
@JmillsExpensify a quick follow up on the payout here. |
$1,000 approved for payment based on BZ summary. |
@dylanexpensify can you please update the title of the issue I think the automation failed here. And this should have been payed 2 weeks ago. |
@dylanexpensify Can we please payout @WikusKriek? If already done, can we close this one out? and I changed my mind about adding regression tests. Regression Test Steps
|
I have not recieved payment yet, is @dylanexpensify maybe OOO? The last time he was active here was almost one month ago. Can we maybe get someone to just do the payment and close this one out? |
Ah let me get it to you now @WikusKriek! Apologies I was ooo! |
done! |
Thanks! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Old IOUs shouldn’t appear above more recent chats, all IOUs should also have modern headers that links back to the parent report to which they are attached.
Actual Result:
Again, the headers are incorrect, the chats are being sorted incorrectly in the LHN vs more recent chats
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.43-7
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
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @JmillsExpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689959205989049
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: