Skip to content

Add auto travel description toggle#80142

Merged
stitesExpensify merged 42 commits intomainfrom
stites-addAutoTravelDescriptionToggle
Feb 10, 2026
Merged

Add auto travel description toggle#80142
stitesExpensify merged 42 commits intomainfrom
stites-addAutoTravelDescriptionToggle

Conversation

@stitesExpensify
Copy link
Contributor

@stitesExpensify stitesExpensify commented Jan 21, 2026

Explanation of Change

Fixed Issues

$ #80019
PROPOSAL: N/A

Tests

  1. Create an account
  2. Create a new workspace
  3. Enable travel
  4. Accept the travel terms
  5. Ensure you see a toggle for descriptions
  6. Ensure the toggle defaults to on
  7. Turn it off and on
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Create an account
  2. Create a new workspace
  3. Enable travel
  4. Accept the travel terms
  5. Ensure you see a toggle for descriptions
  6. Ensure the toggle defaults to on
  7. Create a trip in Expensify Travel
  8. Create an expense during the time of that trip
  9. Ensure that the description is automatically set
  10. Turn off the toggle
  11. Create an expense during the time of that trip
  12. Ensure that the description is NOT automatically set
  13. Turn the toggle back on
  14. Create an expense during the time of that trip
  15. Ensure that the description is automatically set
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari 2026-01-30_16-44-17

@stitesExpensify stitesExpensify self-assigned this Jan 21, 2026
@codecov
Copy link

codecov bot commented Jan 21, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 87.39% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/actions/Policy/Travel.ts 0.00% <0.00%> (ø)
...rc/pages/workspace/travel/BookOrManageYourTrip.tsx 0.00% <0.00%> (ø)
... and 10 files with indirect coverage changes

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@stitesExpensify stitesExpensify changed the title Add auto travel description toggle [HOLD] Add auto travel description toggle Jan 22, 2026
@stitesExpensify
Copy link
Contributor Author

@OSBotify

This comment has been minimized.

@stitesExpensify
Copy link
Contributor Author

Hm okay thanks I'll take a look.

@stitesExpensify
Copy link
Contributor Author

This is the error you're getting which is weird because the policy should have travel settings. Looking into it now. There are also some merge issues and the travel invoicing page is taking over when on a beta, so I'll chat with @blimpich about that

Throw ExpException - 9878a4f504f361ed8b4fa283f60fbfe1 ~~ exceptionMessage: 'Travel must be enabled' exceptionFile: '/git/releases/expensify.com/d577020/lib/PolicyAPI.php' exceptionLine: '3794' exceptionCode: '403'

@stitesExpensify
Copy link
Contributor Author

@thesahindia the issue was caused by the policy being provisioned a long time ago. I have a different PR to fix that, but this specific policy is fixed and you can continue testing

@stitesExpensify stitesExpensify changed the title Add auto travel description toggle [HOLD https://github.com/Expensify/Web-Expensify/pull/50597] Add auto travel description toggle Feb 5, 2026
@thesahindia
Copy link
Member

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp Screenshot 2026-02-04 at 4 59 17 PM
Android: mWeb Chrome Screenshot 2026-02-04 at 5 00 05 PM
iOS: HybridApp Screenshot 2026-02-04 at 5 26 00 PM
iOS: mWeb Safari Screenshot 2026-02-04 at 5 38 57 AM
MacOS: Chrome / Safari Screenshot 2026-02-04 at 5 33 55 AM

@melvin-bot melvin-bot bot requested a review from carlosmiceli February 8, 2026 07:18
@melvin-bot
Copy link

melvin-bot bot commented Feb 8, 2026

@carlosmiceli 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]

carlosmiceli
carlosmiceli previously approved these changes Feb 9, 2026
@stitesExpensify stitesExpensify changed the title [HOLD https://github.com/Expensify/Web-Expensify/pull/50597] Add auto travel description toggle Add auto travel description toggle Feb 10, 2026
@OSBotify

This comment has been minimized.

@OSBotify
Copy link
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 91d872f3..1418d028 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2827,7 +2827,8 @@ ${
                         5. Füge eine eigene Einladung hinzu, wenn du möchtest!
 
                         [Zu den Workspace-Mitgliedern](${workspaceMembersLink}).
-        `),
+
+                    `),
             },
             setupCategoriesAndTags: {
                 title: ({workspaceCategoriesLink, workspaceTagsLink}) => `Richte [Kategorien](${workspaceCategoriesLink}) und [Tags](${workspaceTagsLink}) ein`,
@@ -5170,9 +5171,9 @@ _Für ausführlichere Anweisungen [besuchen Sie unsere Hilfeseite](${CONST.NETSU
                     subtitle: 'Wir prüfen derzeit deine Anfrage zur Aktivierung von Expensify Travel. Keine Sorge, wir sagen dir Bescheid, sobald alles bereit ist.',
                     ctaText: 'Anfrage gesendet',
                 },
-                bookOrManageYourTrip: {title: 'Reisebuchung', subtitle: 'Glückwunsch! Du kannst in diesem Arbeitsbereich jetzt Reisen buchen und verwalten.', ctaText: 'Reisen verwalten'},
+                bookOrManageYourTrip: {title: 'Reisebuchung', subtitle: 'Glückwunsch! Du kannst jetzt in diesem Workspace Reisen buchen und verwalten.', ctaText: 'Reisen verwalten'},
                 settings: {
-                    autoAddTripName: {title: 'Reisenamen zu Ausgaben hinzufügen', subtitle: 'Reisenamen für in Expensify gebuchte Reisen automatisch zu Spesenbeschreibungen hinzufügen.'},
+                    autoAddTripName: {title: 'Reisenamen zu Ausgaben hinzufügen', subtitle: 'Reisenamen automatisch zu Spesenbeschreibungen hinzufügen für in Expensify gebuchte Reisen.'},
                 },
                 travelInvoicing: {
                     centralInvoicingSection: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index e1d986dc..1d7cafcc 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -5181,13 +5181,13 @@ _Pour des instructions plus détaillées, [visitez notre site d’aide](${CONST.
                 },
                 bookOrManageYourTrip: {
                     title: 'Réservation de voyage',
-                    subtitle: 'Félicitations ! Vous êtes prêt à réserver et gérer des voyages dans cet espace de travail.',
+                    subtitle: 'Félicitations ! Vous êtes prêt à réserver et gérer vos déplacements dans cet espace de travail.',
                     ctaText: 'Gérer les déplacements',
                 },
                 settings: {
                     autoAddTripName: {
-                        title: 'Ajouter des noms de voyage aux dépenses',
-                        subtitle: 'Ajouter automatiquement les noms de voyage aux descriptions des dépenses pour les voyages réservés dans Expensify.',
+                        title: 'Ajouter des noms de déplacement aux dépenses',
+                        subtitle: 'Ajouter automatiquement les noms de voyage aux descriptions des dépenses pour les déplacements réservés dans Expensify.',
                     },
                 },
                 travelInvoicing: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 07c930c2..999a54f2 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -5152,14 +5152,10 @@ _Per istruzioni più dettagliate, [visita il nostro sito di assistenza](${CONST.
                     subtitle: 'Stiamo attualmente esaminando la tua richiesta di abilitare Expensify Travel. Non preoccuparti, ti faremo sapere quando sarà pronto.',
                     ctaText: 'Richiesta inviata',
                 },
-                bookOrManageYourTrip: {
-                    title: 'Prenotazione di viaggio',
-                    subtitle: 'Complimenti! Ora sei pronto per prenotare e gestire i viaggi in questo spazio di lavoro.',
-                    ctaText: 'Gestisci viaggi',
-                },
+                bookOrManageYourTrip: {title: 'Prenotazione viaggi', subtitle: 'Complimenti! Ora puoi prenotare e gestire i viaggi in questo spazio di lavoro.', ctaText: 'Gestisci viaggi'},
                 settings: {
                     autoAddTripName: {
-                        title: 'Aggiungi nomi di viaggi alle spese',
+                        title: 'Aggiungi i nomi dei viaggi alle spese',
                         subtitle: 'Aggiungi automaticamente i nomi dei viaggi alle descrizioni delle spese per i viaggi prenotati in Expensify.',
                     },
                 },
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 4b9fbd38..6c8ad69e 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -5117,7 +5117,7 @@ _詳しい手順については、[ヘルプサイトをご覧ください](${CO
                     ctaText: 'リクエストを送信しました',
                 },
                 bookOrManageYourTrip: {title: '出張予約', subtitle: 'おめでとうございます!このワークスペースで旅行の予約と管理を行う準備が整いました。', ctaText: '出張を管理'},
-                settings: {autoAddTripName: {title: '経費に出張名を追加', subtitle: 'Expensifyで予約した出張について、経費の説明に出張名を自動的に追加します。'}},
+                settings: {autoAddTripName: {title: '経費に出張名を追加', subtitle: 'Expensifyで予約した出張について、出張名を経費の説明に自動的に追加します。'}},
                 travelInvoicing: {
                     centralInvoicingSection: {
                         title: '集中請求',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 41e25a41..7443582c 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -5146,13 +5146,12 @@ _Voor meer gedetailleerde instructies, [bezoek onze help-site](${CONST.NETSUITE_
                     subtitle: 'We beoordelen je aanvraag om Expensify Travel in te schakelen. Maak je geen zorgen, we laten je weten wanneer het klaar is.',
                     ctaText: 'Verzoek verzonden',
                 },
-                bookOrManageYourTrip: {
-                    title: 'Boeking van reizen',
-                    subtitle: 'Gefeliciteerd! Je bent helemaal klaar om reizen in deze workspace te boeken en te beheren.',
-                    ctaText: 'Reizen beheren',
-                },
+                bookOrManageYourTrip: {title: 'Reisboeking', subtitle: 'Gefeliciteerd! Je bent helemaal klaar om reizen te boeken en beheren in deze workspace.', ctaText: 'Reizen beheren'},
                 settings: {
-                    autoAddTripName: {title: 'Reisnamen aan uitgaven toevoegen', subtitle: 'Voeg automatisch reisnamen toe aan onkostomemo’s voor reizen die in Expensify zijn geboekt.'},
+                    autoAddTripName: {
+                        title: 'Reisnamen aan onkosten toevoegen',
+                        subtitle: 'Voeg automatisch reissnamen toe aan onkostomschrijvingen voor reizen die in Expensify zijn geboekt.',
+                    },
                 },
                 travelInvoicing: {
                     centralInvoicingSection: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 0d6eeda3..c416024e 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -5140,7 +5140,7 @@ _Aby uzyskać bardziej szczegółowe instrukcje, [odwiedź naszą stronę pomocy
                     ctaText: 'Zarządzaj podróżami',
                 },
                 settings: {
-                    autoAddTripName: {title: 'Dodaj nazwy podróży do wydatków', subtitle: 'Automatycznie dodawaj nazwy podróży do opisów wydatków za podróże zarezerwowane w Expensify.'},
+                    autoAddTripName: {title: 'Dodaj nazwy podróży do wydatków', subtitle: 'Automatycznie dodawaj nazwy podróży do opisów wydatków dla podróży zarezerwowanych w Expensify.'},
                 },
                 travelInvoicing: {
                     centralInvoicingSection: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ec703778..c00ef9dd 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -5139,12 +5139,12 @@ _Para instruções mais detalhadas, [visite nossa central de ajuda](${CONST.NETS
                 },
                 bookOrManageYourTrip: {
                     title: 'Reserva de viagem',
-                    subtitle: 'Parabéns! Você já está pronto para reservar e gerenciar viagens neste workspace.',
+                    subtitle: 'Parabéns! Agora você está pronto para reservar e gerenciar viagens neste workspace.',
                     ctaText: 'Gerenciar viagens',
                 },
                 settings: {
                     autoAddTripName: {
-                        title: 'Adicionar nomes de viagem às despesas',
+                        title: 'Adicionar nomes de viagens às despesas',
                         subtitle: 'Adicione automaticamente os nomes das viagens às descrições das despesas para viagens reservadas no Expensify.',
                     },
                 },
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 0edf673b..6520c4b5 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -5047,8 +5047,8 @@ _如需更详细的说明,请[访问我们的帮助网站](${CONST.NETSUITE_IM
                     subtitle: '我们正在审核你启用 Expensify Travel 的请求。别担心,准备好后我们会通知你。',
                     ctaText: '请求已发送',
                 },
-                bookOrManageYourTrip: {title: '差旅预订', subtitle: '恭喜!您现在可以在此工作区预订和管理差旅了。', ctaText: '管理差旅'},
-                settings: {autoAddTripName: {title: '将行程名称添加到报销单', subtitle: '为在 Expensify 中预订的行程,自动将行程名称添加到报销事由描述中。'}},
+                bookOrManageYourTrip: {title: '差旅预订', subtitle: '恭喜!您已准备就绪,可以在此工作区预订和管理差旅。', ctaText: '管理差旅'},
+                settings: {autoAddTripName: {title: '将行程名称添加到报销费用中', subtitle: '为在 Expensify 中预订的差旅自动将行程名称添加到报销事由中。'}},
                 travelInvoicing: {
                     centralInvoicingSection: {
                         title: '集中开票',

Note

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

View workflow run

@stitesExpensify stitesExpensify merged commit 12b1202 into main Feb 10, 2026
34 checks passed
@stitesExpensify stitesExpensify deleted the stites-addAutoTravelDescriptionToggle branch February 10, 2026 18:36
@github-actions
Copy link
Contributor

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

@OSBotify
Copy link
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
Contributor

🚀 Deployed to staging by https://github.com/stitesExpensify in version: 9.3.17-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.17-9 🚀

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

export {enablePolicyTravel};
function setPolicyTravelSettings(policyID: string, settings: Partial<OnyxTypes.WorkspaceTravelSettings>) {
// eslint-disable-next-line @typescript-eslint/no-deprecated -- Tracked in https://github.com/Expensify/Expensify/issues/507850
const policy = PolicyUtils.getPolicy(policyID);
Copy link
Contributor

Choose a reason for hiding this comment

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

@stitesExpensify This function was deprecated. Can you please pass the policy directly here?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants