-
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
[HOLD for payment 2023-01-23] [$4000] mWeb - Copy to email/URL is not working correctly - reported by @mateusbra #8311
Comments
Triggered auto assignment to @johnmlee101 ( |
@kavimuru I found this issue while working on #8195 and reported on slack here: https://app.slack.com/client/T03SC9DTT/C01GTK53T8Q does that count for reporting bounty? |
@mateusbra I don't have access to the slack. But as per this comment, #8195 (comment) yes. Also tester can repro this bug too #8006 (comment) |
Opening this up! |
Triggered auto assignment to @Christinadobrzyn ( |
This should stay daily priority |
@mateusbra do you have interest in working on this one since you discovered it? Feel free to leave a proposal if so. @kavimuru can you please make sure we at the "@ reported by" to a GH title if they are due the bug reporting bounty? Seems applicable in this case for @mateusbra but maybe I'm not understanding fully? |
@Christinadobrzyn Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Sorry for the delay, i was ooo. Posted job to Upwork; Internal job - https://www.upwork.com/ab/applicants/1508625903649284096/job-details It does look like @mateusbra found/reported this issue so added them to the OP as the reporter. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Triggered auto assignment to @marcochavezf ( |
Hi, |
I don't see how this is different from #8195. This should have been fixed on #8311. cc: @Santhosh-Sellavel @mateusbra why do we need a different issue? |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.54-2 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-01-23. 🎊 After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:
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:
|
@marcochavezf @parasharrajat @b1tjoy please see and complete checklist |
Note: I haven't reviewed the PR for this issue due to unavailability. |
Touching base with @marcochavezf here. |
Completed the BugZero checklist 👍🏽 |
still discussing |
Payments issued. No regression test needed, it's already covered here. |
Am I eligible for partial C+ payment(maybe 50% or 25%) on this issue? Why?
Why not?
|
Sorry for bumping this very old issue. Any comments on #8311 (comment) |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Issue was found when executing #8195
Action Performed:
Expected Result:
The message "Copy e-mail to clipboard" displayed when you try to copy an email and "copy URL to clipboard" tapping URL
Actual Result:
The message "Copy to clipboard" displayed when you try to copy an email. Sometimes it shows as regular context menu
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.46-0
Reproducible in staging?: y
Reproducible in production?: y (New feature)
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5505102_Record_2022-03-25-00-35-55__1_.mp4
screen-20220324-194533.mp4
Expensify/Expensify Issue URL:
Issue reported by: Reported by @mateusbra https://expensify.slack.com/archives/C01GTK53T8Q/p1647474115298459
Slack conversation:
View all open jobs on GitHub
Issue was found when executing #8195
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: