-
Notifications
You must be signed in to change notification settings - Fork 3k
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 @0xmiroslav payment] [$2000] Request Money modal closed when selecting currency for new request or edit #25626
Comments
Triggered auto assignment to @conorpendergrast ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @roryabraham ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Unable to reproduce on latest dev. Am I missing some repro steps? Screen.Recording.2023-08-22.at.4.10.45.AM.mov |
forgot to include this: Screen.Recording.2023-08-21.at.23.46.17.mp4 |
I reproduced on Staging |
I agree that this is a deploy blocker. @mountiny @roryabraham any ideas for which PR caused this? |
@mountiny @conorpendergrast I reproduced this. I can work on this if you're still looking for someone. |
@cubuspl42 We are actively looking into this one, if you have a valid proposal identifying the offending PR (this is a deploy blocker so there must have been a recent change in staging which introduced it), I could let you work on it for $500 |
So far it looks to me like it was always broken with the ("Manual" / "Scan" / "Distance") header, which is under beta. So that would mean it's been broken for weeks. So I guess it's not a release blocker? (But I haven't confirmed this for 100%) |
@mountiny Could you test this with this manual patch? function canUseScanReceipts(betas) {
return false; // <--
return _.contains(betas, CONST.BETAS.SCAN_RECEIPTS) || canUseAllBetas(betas);
} (Maybe same for |
@cubuspl42, Of course, it can be only reproduced with "Manual" / "Scan" / "Distance" header. |
@Pluto0104 But are bugs reproducible only with beta features considered deploy blockers? |
@cubuspl42, Since I'm new to contributing to this project, I may not have a thorough understanding of the beta features yet. However, based on my current knowledge, I don't believe the bug is severe, frequent, or affecting a significant number of users who rely on the beta feature. Therefore, I don't consider it to be a deploy blocker. |
@mountiny Anyway, let me know if we degrade this to a non-blocker and if the work offer you proposed stands. |
The beta worked fine for us for weeks, this is indeed recent |
In general, you are right that beta features might not be considered as deploy blockers. At the moment tho the Scan and Distance are our highest priority so we definitely want to fix this asap. It is also making testing of new features locally where the betas are enabled harder |
Triggered auto assignment to @abekkala ( |
This comment was marked as duplicate.
This comment was marked as duplicate.
@abekkala I'm on parental leave; re-assigning! This is set for payment today and a review to see if @parasharrajat should be considered as reporter too |
@mountiny since this was reported by @parasharrajat on Aug 18 https://expensify.slack.com/archives/C049HHMV9SM/p1692371427006799 |
PAYMENT DETAILS: Reporter: Vit @mountiny I also reviewed the PR - can you confirm the delay was due to QA an bonus is warranted? |
@parasharrajat is a reported I believe This was linked to multiple issues and we did not get this merged that fast, not saying by contirbutors mistake, but I believe the urgency bonus should be really applied when its merged fast as a collective effort. I do not see @0xmiroslav as a reviewer here, @0xmiroslav can you confirm your work on this issue please? thanks! |
Here's context: I reviewed initial proposals and helped testing patch (merged PR) and confirmed that it fixed both issues. |
Thanks |
Payments for today:Reporter: @parasharrajat [$250 as this was reported prior to Aug 30] Gets Paid via EChat @0xmiroslav can you complete the checklist above so I can complete payments? |
|
@shubham1206agra - paid and contract ended! 🎉 Thank You! @0xmiroslav can you accept the offer, in Upwork, so I can submit payment: https://www.upwork.com/nx/wm/offer/26452949 @parasharrajat - payment is made via EChat |
@abekkala sorry please hold my payment yet. I will let you know when ready. |
@abekkala Payment requested as per #25626 (comment) |
@parasharrajat ah yes, I see now that you get paid via Expensify Chat |
not overdue - waiting on further guidance on payment |
$250 payment for @parasharrajat approved based on BZ summary. |
STATUS: Please ping me here when you're able to accept payments in Upwork. |
@0xmiroslav are you ready to accept payments via Upwork yet? |
Let's close this for now. I am tracking locally |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Break down in numbered steps
Expected Result:
Describe what you think should've happened
You are back on the amount page with selected currency
Actual Result:
Describe what actually happened
The modal has closed
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: v1.3.56-0
Reproducible in staging?: Y
Reproducible in production?: N
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: @parasharrajat
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: