Skip to content

[Awaiting Payment 20th May] [Guided Setup Stage 1] Ask for business name before asking for display name #41589

Description

@trjExpensify

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


Version Number: v1.4.70-1
Reproducible in staging?: Y
Reproducible in production?:
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: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1714746065450189?thread_ts=1714400621.865599&cid=C036QM0SLJK

Action Performed:

  1. Sign up with a new account
  2. Click Manage my team's Expenses in the onboarding modal
  3. Observe the next question you're asked is for your display name
  4. Enter your display name
  5. Observe the next question you're asked is for your business name

Expected Result:

When a new user selects the Manage my team's expenses onboarding intent:

  1. The next question we ask should be for their Business name
  2. Upon clicking the confirmation button on the business name page we should trigger the CreateWorkspace API command immediately

Actual Result:

We ask for business name last, so as a result, we trigger the CreateWorkspace command at the end of the onboarding flow.

Workaround:

N/A

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

2024-05-03_15-23-09.mp4

View all open jobs on GitHub

CC: @anmurali @francoisl @NikkiWines @mountiny @danielrvidal

Issue OwnerCurrent Issue Owner: @thesahindia

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Fields

No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions