Skip to content

[Due for payment 2025-05-20] Allow users to schedule calendly calls in App #59747

Closed

Description

@MonilBhavsar

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

Tracking issue #56910
Implement this section of the design doc https://docs.google.com/document/d/1Q_FsNMTX9vKx_pWD75011atzJNV6kGUCBItqyHWVvaw/edit?tab=t.0#bookmark=kix.gbv1cxd24t1i

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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:
Slack conversation (hyperlinked to channel name):

Action Performed:

Break down in numbered steps

Expected Result:

Describe what you think should've happened

Actual Result:

Describe what actually happened

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @sonialiap

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 7, 2025
  2. melvin-bot commented on Apr 7, 2025

    @melvin-bot

    Triggered auto assignment to @sonialiap (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.

  3. added
    NewFeatureSomething to build that is a new item.
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 7, 2025
  4. self-assigned this
    on Apr 7, 2025
  5. melvin-bot commented on Apr 7, 2025

    @melvin-bot

    Current assignee @sonialiap is eligible for the NewFeature assigner, not assigning anyone new.

  6. melvin-bot commented on Apr 7, 2025

    @melvin-bot

    ⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

  7. melvin-bot commented on Apr 7, 2025

    @melvin-bot

    Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (NewFeature)

  8. MonilBhavsar commented on Apr 7, 2025

    @MonilBhavsar
    ContributorAuthor

    This is a part of #sales team, so not tied to any project

  9. 31 remaining items

  10. sonialiap commented on May 20, 2025

    @sonialiap
    Contributor

    Payment summary:

    Not adding regression steps since we will need to add an entire test suite for the new feature

  11. jjcoffee commented on May 29, 2025

    @jjcoffee
    Contributor

    @sonialiap Just to note that the design doc states that this is a CRITICAL issue, so I believe the compensation should be adjusted to $500 for the PR review. (The size of the PR and the extra time required for testing with a lot of back and forth also fits with this I believe!)

  12. mallenexpensify commented on May 29, 2025

    @mallenexpensify
    Contributor

    @jjcoffee , I was experimenting with having CRITICAL issues at $500 for #quality issues. It's not a blanket or company-wide initiative where anything mentioned or labeled as critical is $500.

  13. sonialiap commented on May 29, 2025

    @sonialiap
    Contributor

    With Matt's confirmation that not all critical issues being $500, I'm going to leave the payment at $250 unless you think the scope warrants a higher price @jjcoffee

  14. jjcoffee commented on May 30, 2025

    @jjcoffee
    Contributor

    I was experimenting with having CRITICAL issues at $500 for #quality issues. It's not a blanket or company-wide initiative where anything mentioned or labeled as critical is $500.

    @mallenexpensify Ah sorry I must have misunderstood - good to have it clarified, thanks!

  15. jjcoffee commented on May 30, 2025

    @jjcoffee
    Contributor

    With Matt's confirmation that not all critical issues being $500, I'm going to leave the payment at $250 unless you think the scope warrants a higher price

    @sonialiap I do think the scope warrants a higher price - there was a lot of back and forth required on the PR which made it very time consuming to review and test. I spent more than double the time I would on a "usual" PR.

  16. MonilBhavsar commented on May 30, 2025

    @MonilBhavsar
    ContributorAuthor

    @mallenexpensify @sonialiap

    there was a lot of back and forth required on the PR which made it very time consuming to review and test. I spent more than double the time I would on a "usual" PR.

    I would agree on this and would vote for increasing the price on this PR

  17. mallenexpensify commented on May 30, 2025

    @mallenexpensify
    Contributor

    cool.. cool.. glad we got this sorted. I updated Sonia's payment summary above to

    @jjcoffee $500 please request in NewDot

  18. garrettmknight commented on Jun 5, 2025

    @garrettmknight
    Contributor

    $500 approved for @jjcoffee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionNewFeatureSomething to build that is a new item.ReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions