Closed m-natarajan closed 1 month ago
@youssef-lr A PR for another issue is already in progress and PR is not merged yet so how can I create new PR without affecting that PR? I am not able to see fork option because that one is still in progress.
Bump @eVoloshchak and @youssef-lr to see @kaushiktd comments above. Thanks!
@kaushiktd sorry I'm not following, what other PR is open? does it fix this issue?
A PR for another issue is already in progress and PR is not merged yet so how can I create new PR without affecting that PR?
Ah I think I see, is this about our guidelines to only have one PR in progress?
@youssef-lr I've already submitted PR for this issue and tagged @eVoloshchak there. Do you want to me to tag you there as well?
@youssef-lr Yes but I got it sorted from slack.
This issue has not been updated in over 15 days. @eVoloshchak, @youssef-lr, @isabelastisser, @kaushiktd eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
@eVoloshchak @youssef-lr @kaushiktd, what's next here? Is the PR on hold?
@isabelastisser PR is ready. Waiting for @eVoloshchak review.
Thanks, @kaushiktd! @eVoloshchak, please review the PR. I will DM you for visibility. Thanks!
@eVoloshchak @kaushiktd please provide an update, thanks!
@isabelastisser working on new PR
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.7-8 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-07-24. :confetti_ball:
For reference, here are some details about the assignees on this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
Triggered auto assignment to @isabelastisser (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
Triggered auto assignment to @alexpensify (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
I will be OOO tomorrow and next week, so I am reassigning this until I return on July 29. Thanks, @alexpensify
Status:
Noted, I'll prepare next week for the payment date.
Not overdue, the payment date is on the 24th.
Correct me if I'm wrong, but it looks like there is another PR in the works associated with this GH: https://github.com/Expensify/App/pull/45333. I'm going to hold off on completing the payment action until all PRs are in production.
@kaushiktd - please apply here: https://www.upwork.com/jobs/~016c93f917170cbc76
Thanks!
@alexpensify Is it possible for you to send me an invitation to that job?
@kaushiktd - I sent an invite via Upwork. Please accept and I can complete the payment process. Thanks!
Thank you @alexpensify
I accepted the offer.
Done - I've completed the payment process in Upwork
https://github.com/Expensify/App/issues/41763#issuecomment-2248625040
@eVoloshchak - please submit a request in Chat, thanks!
Thanks for handling this, @alexpensify!
You're welcome! @isabelastisser there is no more action to take here.
@eVoloshchak - please submit a request in Chat. 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!
Version Number: 1.4.71-0 Reproducible in staging?: y Reproducible in production?: new feature 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: Applause internal team Slack conversation:
Action Performed:
Expected Result:
The split amount will be reset (mweb behavior when keyboard is up).
Actual Result:
The keyboard is dismissed and the split amount is not reset.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/bc3628b3-3d50-4a64-aff8-c68eef43c839
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @alexpensify