Skip to content

[Due for payment 2026-09-02] New user landing + missing "Send to someone" option after creating first expense #97881

Closed

Description

@melvin-bot

Problem

When a brand-new user signs up, selects "Something else" on the onboarding screen (i.e. effectively selects nothing), and then creates an expense, two things happen that seem off:

  1. Landing location — After creating the expense, the user lands in their Personal Space (Inbox), rather than in Spend > Expenses.
  2. Missing "Send to someone" action — When viewing the newly created expense, the "Send to someone" option is not available under More. It's expected to be there and to use the same flow that's available from the Inbox.

Expected behavior

  1. After creating the first expense, the user should land in Spend > Expenses (not Personal Space).
  2. The "Send to someone" option should be available under More when viewing the expense, using the same flow as from the Inbox.

Actual behavior

  1. User lands in Personal Space.
  2. "Send to someone" is missing from the More menu on the expense.

Platform

Web (desktop) — reproduced by selecting "Something else" during onboarding.

Reported in Slack.

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. self-assigned this
    on Aug 5, 2026
  2. shawnborton commented on Aug 7, 2026

    @shawnborton
    Contributor
  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Aug 14, 2026
  4. melvin-bot commented on Aug 14, 2026

    @melvin-bot
    Author

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia (External)

  5. melvin-bot commented on Aug 14, 2026

    @melvin-bot
    Author
  6. shawnborton commented on Aug 14, 2026

    @shawnborton
    Contributor

    Assigning Kevin as he has been reviewing the PR.

  7. shawnborton commented on Aug 21, 2026

    @shawnborton
    Contributor

    I realized we didn't add the "Send to my employer" option - going to make a follow up PR for that.

  8. melvin-bot commented on Aug 21, 2026

    @melvin-bot
    Author

    @ikevin127 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  9. 14 remaining items

  10. changed the title [-][Due for payment 2026-08-29] New user landing + missing "Send to someone" option after creating first expense[/-] [+][Due for payment 2026-09-02] New user landing + missing "Send to someone" option after creating first expense[/+] on Aug 26, 2026
  11. melvin-bot commented on Aug 26, 2026

    @melvin-bot
    Author

    @ikevin127

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.61-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 2026-09-02. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  12. ikevin127 commented on Aug 28, 2026

    @ikevin127
    Contributor

    @mallenexpensify

    TLDR: Payment summary for $500 is due first on 2026-08-29, second summary ($125 - had 1 regression) is due on 2026-09-02.

    Note this decision and the BZ checklist for the first PR on this issue - payment summary for $500 is due for me on 2026-08-29.

    The second PR 👆 mentioned in that same decision was just deployed - of which automation updated the payment due date to 2026-09-02, this will be the second payment date since nobody created a separate issue as per that decision.

  13. melvin-bot commented on Aug 31, 2026

    @melvin-bot
    Author

    @ikevin127 Whoops! This issue is 2 days overdue. Let's get this updated quick!

  14. ikevin127 commented on Sep 1, 2026

    @ikevin127
    Contributor

    @mallenexpensify No changes from my last comment, awaiting payment due date for 29th (overdue) and second one for 2nd of September.

  15. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 1, 2026
  16. melvin-bot commented on Sep 1, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  17. melvin-bot commented on Sep 1, 2026

    @melvin-bot
    Author

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  18. ikevin127 commented on Sep 1, 2026

    @ikevin127
    Contributor

    Correction to the automation above as posted before 👇

    @mallenexpensify

    TLDR: Payment summary for $500 is due first on 2026-08-29, second summary ($125 - had 1 regression) is due on 2026-09-02.

    Note this decision and the BZ checklist for the first PR on this issue - payment summary for $500 is due for me on 2026-08-29.

    The second PR 👆 mentioned in that same decision was just deployed - of which automation updated the payment due date to 2026-09-02, this will be the second payment date since nobody created a separate issue as per that decision.

  19. mallenexpensify commented on Sep 3, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @ikevin127 due $625 via NewDot

    Thx for the breakdown @ikevin127

  20. quinthar commented on Sep 12, 2026

    @quinthar
    Contributor

    Approved $625 to @ikevin127

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 productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions