You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-05-20] Allow users to schedule calendly calls in App #59747
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:
⚠️ 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 ⚠️
@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!)
@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.
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
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!
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.
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
Activity
melvin-bot commentedon Apr 7, 2025
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.melvin-bot commentedon Apr 7, 2025
Current assignee @sonialiap is eligible for the NewFeature assigner, not assigning anyone new.
melvin-bot commentedon Apr 7, 2025
melvin-bot commentedon Apr 7, 2025
Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (
NewFeature)MonilBhavsar commentedon Apr 7, 2025
This is a part of #sales team, so not tied to any project
31 remaining items
sonialiap commentedon May 20, 2025
Payment summary:
Not adding regression steps since we will need to add an entire test suite for the new feature
jjcoffee commentedon May 29, 2025
@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!)
mallenexpensify commentedon May 29, 2025
@jjcoffee , I was experimenting with having CRITICAL issues at $500 for
#qualityissues. It's not a blanket or company-wide initiative where anything mentioned or labeled ascriticalis $500.sonialiap commentedon May 29, 2025
With Matt's confirmation that not all
criticalissues being $500, I'm going to leave the payment at $250 unless you think the scope warrants a higher price @jjcoffeejjcoffee commentedon May 30, 2025
@mallenexpensify Ah sorry I must have misunderstood - good to have it clarified, thanks!
jjcoffee commentedon May 30, 2025
@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.
MonilBhavsar commentedon May 30, 2025
@mallenexpensify @sonialiap
I would agree on this and would vote for increasing the price on this PR
mallenexpensify commentedon May 30, 2025
cool.. cool.. glad we got this sorted. I updated Sonia's payment summary above to
garrettmknight commentedon Jun 5, 2025
$500 approved for @jjcoffee