-
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-19] [$2000] Feature Request: Open link in Desktop app if it is installed and not in browser #10893
Comments
Triggered auto assignment to @stephanieelliott ( |
@stephanieelliott Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Sounds cool, passing this on to engineering! |
Triggered auto assignment to @madmax330 ( |
@MonilBhavsar I think this can be external yeah? |
Yes 👍 |
Cool |
Triggered auto assignment to @michaelhaxhiu ( |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
PR is merged, and awaiting deployment! |
I'll take this GH back @mallenexpensify thank you for watching it! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.52-4 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-19. 🎊 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:
|
We can continue the discussion regarding the bounty increase request on this one while we wait the regression period. cc: @cowboycito |
@Santhosh-Sellavel how should we proceed for payment? |
@cowboycito But then we are not sure about how long/complex it might take, I've replied here
Now the job is done I've initiated the discussion here waiting for it CM. Meanwhile, let us know what you think is a fair amount. I'll post internally let us get it sorted thanks! |
@Santhosh-Sellavel do you want to post the increased compensation request first then @cowboycito can 👍 or comment? I think that'd be easiest. Please include the amount total you think is fair. Provide reasoning, including links and details. That will make it easy for the BZ / @Christinadobrzyn to 👍 (if they agree). Thanks. |
Hey @cowboycito - what compensation amount do you think is fair for this job? |
Sorry for the delay everyone, I'll post a summary of events by date. Pretty same we got the proposal kick-started from @cowboycito here After review and some discussions, I've requested additional changes i.e requested POC to completely test the code on 7 Nov 2022 here. On the same day, @cowboycito questioned about an increase in bounty here. I thought it's fair to raise bounty since I'm not sure about how much work is left out, so commented here let's discuss once the job is complete. On 10 Nov 2022 here the POC is ready for review. After some discussions and review. On 25 Nov 2022 here, I was able to verify the POC. And a design request for a deep link page was initiated. The proposal was updated by @cowboycito on Dec 1 here And I recommended hire here on the same day. Also, I noticed a bug on safari while reviewing. 9 Dec 2022 12 Dec 2022 Ignoring the bug, we have a lot to ship here so we decided to move forward here and here 15 Dec 2022 PR Submitted 23 Dec 2022 Here I requested to flag this one as a penalty as its feature might take more time. 25 Dec 2022 to Jan 2 No activity due to Holiday. Resumed Review Activity Jan 3 PR was merged on Jan 10. Considering the efforts made here, IMO $5K is a fair amount here. |
Sorry for the delay everyone! I agree with what @Santhosh-Sellavel said and I think that sounds fair. |
Thanks @Santhosh-Sellavel and @cowboycito! @NikkiWines does this sound good to you? |
Context https://expensify.slack.com/archives/C01GTK53T8Q/p1674481724781139 I think this PR has a bug: whenever I reload the website, I get the
|
Discussion outcome we decided to create a new issue to sort this one as it occurs only for developers. |
Yep, seems reasonable to me! This was a tricky issue and both @cowboycito and @Santhosh-Sellavel did a good job of keeping it moving and following through to get it across the finish line 👍 |
Okay! ready to close this out:
please let me know if there are any questions! |
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:
Link should open in Desktop app
Actual Result:
Link always open in browser
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
For users:
They can still use the app on web and then move to desktop
For contributors:
None
I think contributors are not able to test the workflow on the desktop app
Platform:
Where is this issue occurring?
Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Upwork job URL: https://www.upwork.com/jobs/~01c5b3dd89b6a749b1
Issue reported by: @MonilBhavsar
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1662630927711119
View all open jobs on GitHub
Slack handles this nicely! If desktop app is installed, Link opens in app and they ask if one wants to open it in the browser.
The text was updated successfully, but these errors were encountered: