Skip to content

Add Travel setup task to Getting Started section - #97133

Merged
blimpich merged 8 commits into
mainfrom
blimpich-travelGettingStartedTask
Jul 28, 2026
Merged

Add Travel setup task to Getting Started section#97133
blimpich merged 8 commits into
mainfrom
blimpich-travelGettingStartedTask

Conversation

@blimpich

@blimpich blimpich commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Coming from this slack thread. Admins who turn on the Travel workspace feature (via onboarding or Workspace Settings) but never complete the one-time Spotnana provisioning process are left with Travel "enabled" but never actually usable by their employees, with no reminder to finish setup. This adds a "Setup travel" task to the home screen's Getting Started section, following the same pattern as the existing "Issue Expensify cards" / "Link company cards" rows: it appears once Travel is enabled on the policy, and clears once the workspace is provisioned (travelSettings.spotnanaCompanyID set).

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/664889
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Log in to staging.new.expensify.com as the admin of a workspace that is within its Getting Started window (created less than 60 days ago) and does not have Travel enabled.
  2. Go to Settings > Workspaces > [workspace] > More features and enable the Travel toggle.
  3. Return to the Home screen.
    • Verify a "Setup travel" task appears in the Getting Started section.
  4. Click the "Setup travel" task.
    • Verify it navigates to staging.new.expensify.com/workspaces/[policyID]/travel.
  5. Complete the Travel provisioning flow (accept the Spotnana terms) for the workspace.
  6. Return to the Home screen.
    • Verify the "Setup travel" task is now marked as complete.
  7. Go to Settings > Workspaces > [workspace] > More features and disable the Travel toggle, then re-enable it.
  8. Return to the Home screen.
    • Verify the "Setup travel" task reappears in the Getting Started section (same behavior as the existing "Issue Expensify cards" / "Link company cards" tasks). It should be marked as already completed.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Screenshot 2026-07-27 at 12 03 18 PM Screenshot 2026-07-27 at 12 30 23 PM

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index b93ce71ab13..6c813111c4b 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1090,6 +1090,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: 'Sprechen Sie mit Ihrer Kundenbetreuung',
             forGuidedSetup: 'für die geführte Einrichtung.',
             configureApprovalsSubText: 'Berichtsfreigaben festlegen',
+            setupTravel: 'Reisen einrichten',
+            setupTravelSubText: 'Reisespezifische Regeln konfigurieren',
         },
         freeTrialSection: {
             title: ({days}: {days: number}) => `Kostenlose Testversion: Noch ${days} ${days === 1 ? 'Tag' : 'Tage'}!`,
diff --git a/src/languages/es.ts b/src/languages/es.ts
index e1f165ef66e..4b3623e32ce 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -1060,6 +1060,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToConcierge: 'Habla con Concierge',
             forGuidedSetup: 'para la configuración guiada.',
             configureApprovalsSubText: 'Definir aprobaciones de informes',
+            setupTravel: 'Configurar viajes',
+            setupTravelSubText: 'Configura reglas específicas de viaje',
         },
         upcomingTravel: 'Próximos viajes',
         upcomingTravelSection: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 4a03311fb6a..67a8b2abaaa 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1106,6 +1106,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: 'Parlez à votre chargé de compte',
             forGuidedSetup: 'pour la configuration guidée.',
             configureApprovalsSubText: 'Définir les approbations de notes de frais',
+            setupTravel: 'Configurer les déplacements',
+            setupTravelSubText: 'Configurer des règles spécifiques aux déplacements',
         },
         yourSpend: {
             title: 'Vos dépenses',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 87989bbae72..cc5d2f945bf 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1104,6 +1104,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: 'Parla con il tuo account executive',
             forGuidedSetup: 'per la configurazione guidata.',
             configureApprovalsSubText: 'Definisci le approvazioni dei report',
+            setupTravel: 'Configura viaggi',
+            setupTravelSubText: 'Configura regole specifiche per i viaggi',
         },
         yourSpend: {
             title: 'Le tue spese',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 4e01b43eb90..82a787825bc 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1086,6 +1086,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: 'アカウントエグゼクティブに相談する',
             forGuidedSetup: 'ガイド付きセットアップ用です。',
             configureApprovalsSubText: 'レポート承認を定義する',
+            setupTravel: '出張を設定',
+            setupTravelSubText: '出張用のルールを設定する',
         },
         yourSpend: {
             title: 'あなたの支出',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 611eed20ce1..278394f1290 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1102,6 +1102,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: 'Praat met je accountmanager',
             forGuidedSetup: 'voor begeleide installatie.',
             configureApprovalsSubText: 'Definieer rapportgoedkeuringen',
+            setupTravel: 'Reizen instellen',
+            setupTravelSubText: 'Reisspecifieke regels instellen',
         },
         yourSpend: {
             title: 'Je uitgaven',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index c7708ce59b3..aec95ffb528 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1100,6 +1100,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: 'Porozmawiaj ze swoim opiekunem klienta',
             forGuidedSetup: 'z prowadzeniem konfiguracji.',
             configureApprovalsSubText: 'Zdefiniuj zatwierdzanie raportów',
+            setupTravel: 'Skonfiguruj podróże',
+            setupTravelSubText: 'Skonfiguruj zasady dotyczące podróży',
         },
         yourSpend: {
             title: 'Twoje wydatki',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index f3364881612..e1a61e4e8a2 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1102,6 +1102,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: 'Fale com seu executivo de contas',
             forGuidedSetup: 'para configuração guiada.',
             configureApprovalsSubText: 'Definir aprovações de relatórios',
+            setupTravel: 'Configurar viagem',
+            setupTravelSubText: 'Configurar regras específicas de viagem',
         },
         yourSpend: {
             title: 'Seus gastos',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 22f87d88446..958bddca1a1 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1069,6 +1069,8 @@ const translations: TranslationDeepObject<typeof en> = {
             talkToAccountExecutive: '联系您的客户经理',
             forGuidedSetup: '以获取引导式设置。',
             configureApprovalsSubText: '定义报表审批',
+            setupTravel: '设置差旅',
+            setupTravelSubText: '配置差旅专用规则',
         },
         yourSpend: {title: '您的支出', awaitingApproval: '等待审批', repaidLast30Days: '过去30天内已偿还', recentTransactions: ({lastFour}: {lastFour: string}) => `最近交易 • ${lastFour}`},
         seeMore: ({count}: {count: number}) => `再查看 ${count} 个`,

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

🚧 blimpich has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@github-actions

Copy link
Copy Markdown
Contributor

🚧 blimpich has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@blimpich
blimpich marked this pull request as ready for review July 27, 2026 19:32
@blimpich
blimpich requested review from a team as code owners July 27, 2026 19:32
@melvin-bot
melvin-bot Bot requested review from abzokhattab and removed request for a team July 27, 2026 19:32
@melvin-bot

melvin-bot Bot commented Jul 27, 2026

Copy link
Copy Markdown

@abzokhattab Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot requested a review from JmillsExpensify July 27, 2026 19:32
@blimpich
blimpich requested review from a team and rlinoz and removed request for JmillsExpensify July 27, 2026 19:32
@melvin-bot
melvin-bot Bot requested review from daledah and removed request for a team July 27, 2026 19:32
@melvin-bot

melvin-bot Bot commented Jul 27, 2026

Copy link
Copy Markdown

@daledah Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team July 27, 2026 19:32
@blimpich
blimpich removed the request for review from abzokhattab July 27, 2026 19:32
@blimpich
blimpich requested a review from a team July 27, 2026 19:32
@melvin-bot
melvin-bot Bot requested review from linhvovan29546 and removed request for a team July 27, 2026 19:32
@melvin-bot

melvin-bot Bot commented Jul 27, 2026

Copy link
Copy Markdown

@linhvovan29546 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@blimpich

Copy link
Copy Markdown
Contributor Author

@daledah @abzokhattab @linhvovan29546 please ignore the ping

@blimpich
blimpich requested a review from stitesExpensify July 27, 2026 19:33

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 618cb57592

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@stitesExpensify stitesExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@blimpich
blimpich merged commit a578faf into main Jul 28, 2026
49 of 50 checks passed
@blimpich
blimpich deleted the blimpich-travelGettingStartedTask branch July 28, 2026 00:09
@github-actions

Copy link
Copy Markdown
Contributor

🚧 blimpich has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/blimpich in version: 9.4.46-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site review — no changes required

I reviewed this PR against App/docs/articles and concluded no help site updates are needed. I did not open a docs PR.

What this PR does: adds a conditional Setup travel task to the Home Getting started checklist. It appears once Travel is enabled on the policy and clears once the workspace is provisioned (travelSettings.spotnanaCompanyID set) — the same pattern as the existing Issue Expensify cards / Link company cards rows.

Why no docs change:

  • The only article documenting the Getting started checklist is Expensify-Home-Overview.md. It describes the section generically — "The checklist items vary based on the intent selected during onboarding" — and does not enumerate individual tasks. The four existing conditional rows (Issue Expensify cards, Link company cards, Configure approval workflow, Set up spend rules) are already not listed there, so adding Setup travel creates no new documentation gap.
  • The travel setup flow itself is unchanged. Enabling and provisioning Travel is already covered by Enable-Travel-on-a-Workspace.md (toggle on under More features, then accept the travel terms). This PR only adds a UI reminder to finish that existing flow — it doesn't introduce new capabilities, settings, or steps to document.

Per the authoring guidelines (one workflow per article, UI-exact labels, no feature-hub padding), adding a line for a single conditional onboarding nudge to the general overview article would go against the article's intentional altitude, so I've left it as-is.

If you'd prefer the overview article to explicitly call out the Setup travel task anyway, reply and I'll open the draft PR.


@blimpich — no linked help site PR was created because I found no required docs change. If you disagree, let me know and I'll draft one.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants