-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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 2023-08-28] [$1000] splitting bill with phone account shows @expensify.sms #22999
Comments
Triggered auto assignment to @MitchExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
PROPOSALPlease re-state the problem that we are trying to solve in this issue.splitting bill with phone account shows @expensify.sms What is the root cause of that problem?Root cause of the issue is that in split bill flow, when we are fetching the payee's personal details by the method App/src/libs/OptionsListUtils.js Lines 878 to 894 in 60f4817
What changes do you think we should make in order to solve the problem?We need to format the alternate text and display name fields using What alternative solutions did you explore? (Optional)We can find other inconsistencies (if any) and fix them all at once |
Commented in Slack |
@MitchExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Confirmed @expensify.sms is not expected to be shown anywhere in app |
Job added to Upwork: https://www.upwork.com/jobs/~0128597348b75205c2 |
Current assignee @MitchExpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @0xmiroslav ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.If the payee is logged in using phone number, then @expensify.sms should not be displayed while splitting bill after login id. What is the root cause of that problem?The login information is displayed plainly from props without formatting and as it has the format What changes do you think we should make in order to solve the problem?In the function App/src/libs/OptionsListUtils.js Lines 905 to 921 in cd851d0
Finally :What alternative solutions did you explore? (Optional)NA |
One note to the internal engineer eventually assigned - Lets double check if we're actively removing @expensify.sms from the front end or the back end across the board just to be 100% sure |
Friendly reminder to review the existing proposals @0xmiroslav 👍 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@0xmiroslav pls review the proposals 😅 |
@MitchExpensify @0xmiroslav this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
reviewing now |
Bump: @0xmiroslav |
📣 @situchan 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
🎯 ⚡️ Woah @situchan / @chiragxarora, great job pushing this forwards! ⚡️ The pull request got merged within 3 working days of assignment, so this job is eligible for a 50% #urgency bonus 🎉
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.55-8 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 2023-08-28. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
Bump on the BZ steps @situchan |
Payment summary: Reporting: @chiragxarora $250 (Upwork) |
Paid! |
@MitchExpensify, @stitesExpensify, @chiragxarora, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Regarding BZ checklist: |
Great, thanks for confirming @situchan - All done here! |
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: @expensify.sms should not be shown
Actual Result:
@expensify.sms should is shown
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: 1.3.41-2
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
bandicam.2023-07-14.14-53-13-346.mp4
Expensify/Expensify Issue URL:
Issue reported by: @chiragxarora
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688810314872429
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: