Skip to content

Conversation

@mhawryluk
Copy link
Contributor

@mhawryluk mhawryluk commented Jan 23, 2026

Explanation of Change

Creates a new workspace settings page for the Time Tracking feature as well as a new RHP for setting default hourly rate.

Fixed Issues

$ #77523
PROPOSAL: N/A

Tests

  1. Log in to an account that has timeTracking beta enabled.
  2. Go to Workspaces > Click on a workspace that has Time Tracking enabled.
  3. There should be a new "Time" tab on the initial page, click on it.
  4. The default hourly rate row should show the current rate (same as in Old Dot), properly formatted and in the workspace's currency.
  5. Click on the row.
  6. Enter a new value and click "save".
  7. Check if the rate was updated by creating a new time expense in this workspace's chat and seeing if the default rate is the one just set.
  8. Also check if in Old Dot the rate is updated to the new value.

Offline tests

After updating the default rate when offline, the default hourly rate menu item should be greyed out until back online. The rate should be updated optimistically.

QA Steps

Same as tests.

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
    • 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
Nagranie.z.ekranu.2026-01-27.o.17.48.56.mov
Android: mWeb Chrome
Nagranie.z.ekranu.2026-01-27.o.17.42.04.mov
iOS: Native
Simulator.Screen.Recording.-.iPhone.16.Pro.Max.-.2026-01-27.at.17.37.15.mp4
iOS: mWeb Safari
Simulator.Screen.Recording.-.iPhone.16.Pro.Max.-.2026-01-27.at.17.39.45.mp4
MacOS: Chrome / Safari
Nagranie.z.ekranu.2026-01-23.o.13.02.45.mov

@melvin-bot
Copy link

melvin-bot bot commented Jan 23, 2026

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@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 9dbe2a90..0735fc47 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -5239,7 +5239,12 @@ _Für ausführlichere Anweisungen [besuchen Sie unsere Hilfeseite](${CONST.NETSU
                 title: 'Regeln',
                 subtitle: 'Belege verlangen, hohe Ausgaben kennzeichnen und mehr.',
             },
-            timeTracking: {title: 'Zeit', subtitle: 'Legen Sie einen abrechenbaren Stundensatz fest, damit Mitarbeitende für ihre Zeit bezahlt werden.'},
+            timeTracking: {
+                title: 'Zeit',
+                subtitle: 'Legen Sie einen abrechenbaren Stundensatz fest, damit Mitarbeitende für ihre Zeit bezahlt werden.',
+                defaultHourlyRate: 'Standardstundensatz',
+                defaultHourlyRateSubtitle: 'Legen Sie einen abrechenbaren Stundensatz für die Zeiterfassung fest.',
+            },
         },
         reports: {
             reportsCustomTitleExamples: 'Beispiele:',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 8e5ea4c8..defa7a5b 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -5247,7 +5247,12 @@ _Pour des instructions plus détaillées, [visitez notre site d’aide](${CONST.
                 title: 'Règles',
                 subtitle: 'Exigez des reçus, signalez les dépenses élevées, et plus encore.',
             },
-            timeTracking: {title: 'Heure', subtitle: 'Définissez un taux horaire facturable pour que les employés soient rémunérés pour leur temps.'},
+            timeTracking: {
+                title: 'Heure',
+                subtitle: 'Définissez un taux horaire facturable pour que les employés soient rémunérés pour leur temps.',
+                defaultHourlyRate: 'Taux horaire par défaut',
+                defaultHourlyRateSubtitle: 'Définissez un taux horaire facturable pour le suivi du temps.',
+            },
         },
         reports: {
             reportsCustomTitleExamples: 'Exemples :',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index ee09a7f6..5786e5d4 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -5226,7 +5226,12 @@ _Per istruzioni più dettagliate, [visita il nostro sito di assistenza](${CONST.
                 title: 'Regole',
                 subtitle: 'Richiedi ricevute, segnala spese elevate e altro ancora.',
             },
-            timeTracking: {title: 'Ora', subtitle: 'Imposta una tariffa oraria fatturabile per consentire ai dipendenti di essere pagati per il loro tempo.'},
+            timeTracking: {
+                title: 'Ora',
+                subtitle: 'Imposta una tariffa oraria fatturabile per consentire ai dipendenti di essere pagati per il loro tempo.',
+                defaultHourlyRate: 'Tariffa oraria predefinita',
+                defaultHourlyRateSubtitle: 'Imposta una tariffa oraria fatturabile per il monitoraggio del tempo.',
+            },
         },
         reports: {
             reportsCustomTitleExamples: 'Esempi:',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index a4aecc65..2e1769ae 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -5192,7 +5192,12 @@ _より詳しい手順については、[ヘルプサイトをご覧ください
                 title: 'ルール',
                 subtitle: 'レシートの必須化や高額支出のフラグ付けなどを設定できます。',
             },
-            timeTracking: {title: '時間', subtitle: '従業員が作業時間に対して支払いを受けられるよう、時間単位の請求レートを設定します。'},
+            timeTracking: {
+                title: '時間',
+                subtitle: '従業員が作業時間に対して支払いを受けられるよう、時間単位の請求レートを設定します。',
+                defaultHourlyRate: 'デフォルトの時間単価',
+                defaultHourlyRateSubtitle: 'タイムトラッキング用の時間単価請求レートを設定します。',
+            },
         },
         reports: {
             reportsCustomTitleExamples: '例:',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 5b0db59e..90168e06 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -5215,7 +5215,12 @@ _Voor gedetailleerdere instructies, [bezoek onze helpsite](${CONST.NETSUITE_IMPO
                 title: 'Regels',
                 subtitle: 'Vereis bonnetjes, markeer hoge uitgaven en meer.',
             },
-            timeTracking: {title: 'Tijd', subtitle: 'Stel een uurtarief in waarmee medewerkers worden betaald voor hun tijd.'},
+            timeTracking: {
+                title: 'Tijd',
+                subtitle: 'Stel een uurtarief in waarmee medewerkers worden betaald voor hun tijd.',
+                defaultHourlyRate: 'Standaard uurtarief',
+                defaultHourlyRateSubtitle: 'Stel een factureerbaar uurtarief in voor tijdregistratie.',
+            },
         },
         reports: {
             reportsCustomTitleExamples: 'Voorbeelden:',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index dea21683..f8e390b8 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -5208,7 +5208,12 @@ _Aby uzyskać bardziej szczegółowe instrukcje, [odwiedź naszą stronę pomocy
                 title: 'Zasady',
                 subtitle: 'Wymagaj paragonów, oznaczaj wysokie wydatki i nie tylko.',
             },
-            timeTracking: {title: 'Czas', subtitle: 'Ustaw godzinową stawkę rozliczeniową, aby pracownicy byli wynagradzani za swój czas.'},
+            timeTracking: {
+                title: 'Czas',
+                subtitle: 'Ustaw godzinową stawkę rozliczeniową, aby pracownicy byli wynagradzani za swój czas.',
+                defaultHourlyRate: 'Domyślna stawka godzinowa',
+                defaultHourlyRateSubtitle: 'Ustaw godzinową stawkę rozliczeniową do śledzenia czasu.',
+            },
         },
         reports: {
             reportsCustomTitleExamples: 'Przykłady:',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index a4c33c47..fd197d90 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -5208,7 +5208,12 @@ _Para instruções mais detalhadas, [visite nosso site de ajuda](${CONST.NETSUIT
                 title: 'Regras',
                 subtitle: 'Exigir recibos, sinalizar gastos elevados e muito mais.',
             },
-            timeTracking: {title: 'Hora', subtitle: 'Defina uma taxa horária faturável para que os funcionários sejam pagos pelo tempo trabalhado.'},
+            timeTracking: {
+                title: 'Hora',
+                subtitle: 'Defina uma taxa horária faturável para que os funcionários sejam pagos pelo tempo trabalhado.',
+                defaultHourlyRate: 'Taxa horária padrão',
+                defaultHourlyRateSubtitle: 'Defina uma taxa horária faturável para o controle de tempo.',
+            },
         },
         reports: {
             reportsCustomTitleExamples: 'Exemplos:',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index cefb15fb..fb252882 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -5102,7 +5102,12 @@ _如需更详细的说明,请[访问我们的帮助网站](${CONST.NETSUITE_IM
                 title: '规则',
                 subtitle: '要求收据、标记高额支出等。',
             },
-            timeTracking: {title: '时间', subtitle: '为员工设置按小时计费的费率,以便根据他们的工作时间获得报酬。'},
+            timeTracking: {
+                title: '时间',
+                subtitle: '为员工设置按小时计费的费率,以便根据他们的工作时间获得报酬。',
+                defaultHourlyRate: '默认时薪',
+                defaultHourlyRateSubtitle: '为时间跟踪设置按小时计费费率。',
+            },
         },
         reports: {
             reportsCustomTitleExamples: '示例:',

Note

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

@codecov
Copy link

codecov bot commented Jan 27, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
...mponents/FocusTrap/WIDE_LAYOUT_INACTIVE_SCREENS.ts 0.00% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
...gation/linkingConfig/RELATIONS/WORKSPACE_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 75.00% <ø> (ø)
...s/iou/request/step/IOURequestStepTimeWorkspace.tsx 0.00% <ø> (ø)
src/pages/workspace/WorkspacePageWithSections.tsx 73.61% <100.00%> (+0.37%) ⬆️
src/pages/workspace/withPolicy.tsx 100.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 7.83% <0.00%> (-0.02%) ⬇️
... and 12 more
... and 3 files with indirect coverage changes

@shawnborton
Copy link
Contributor

NAB at all but cc @Expensify/design - I wonder if we should consider making our clock icon have some more negative space around it? It's pretty beefy compared to say the cash icon. I think our credit card icon has a similar issue. Nothing we need to fix here, but just something we should keep in mind.

@github-actions
Copy link
Contributor

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

@github-actions

This comment has been minimized.

@shawnborton
Copy link
Contributor

Just to make sure I am following, we aren't planning to add Time tracking to the More features page? I enabled the beta but I haven't seen it there yet, though maybe I just need to wait longer :)

@mhawryluk
Copy link
Contributor Author

Just to make sure I am following, we aren't planning to add Time tracking to the More features page? I enabled the beta but I haven't seen it there yet, though maybe I just need to wait longer :)

hmm, it should be there, the PR adding it was merged yesterday

Zrzut ekranu 2026-01-27 o 18 03 48

@shawnborton
Copy link
Contributor

Sounds good, I'll wait a bit until the beta kicks in then.

Also, cc @jamesdeanexpensify - did you work on the copy for that feature? I wonder if we could shorten it a tad (the description text under Time)

@mhawryluk
Copy link
Contributor Author

mhawryluk commented Jan 27, 2026

Sounds good, I'll wait a bit until the beta kicks in then.

Also, cc @jamesdeanexpensify - did you work on the copy for that feature? I wonder if we could shorten it a tad (the description text under Time)

it's Set an hourly billable rate for time tracking on Figma, but Set an hourly billable rate for employees to get paid for their time. in the design doc. I went with the latter, but I'm actually not sure which one is newer, so clarification would be great 😅

@shawnborton
Copy link
Contributor

Okay got it working, seems to be good. Let's just get confirmation on the copy 👍

@shawnborton
Copy link
Contributor

It looks like enabling and disabling the Time feature isn't posting to the #admins room of the workspace... is that known? It should post updates like these:
CleanShot 2026-01-28 at 05 39 55@2x

@shawnborton
Copy link
Contributor

Friendly bump on the copy when you can @jamesdeanexpensify

@mhawryluk
Copy link
Contributor Author

It looks like enabling and disabling the Time feature isn't posting to the #admins room of the workspace... is that known? It should post updates

thanks, I didn't notice this. @grgia I think it's a backend issue, right?

@grgia
Copy link
Contributor

grgia commented Jan 28, 2026

@jnowakow has been working on updates to that flow

src/SCREENS.ts Outdated
PER_DIEM_EDIT_AMOUNT: 'Per_Diem_Edit_Amount',
PER_DIEM_EDIT_CURRENCY: 'Per_Diem_Edit_Currency',
TIME_TRACKING: 'Time_Tracking',
TIME_TRACKING_RATE: 'Time_Tracking_Rate',
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's rename TIME_TRACKING_DEFAULT_RATE

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sure, should the route stay as /rate or should that be /default-rate too?

Copy link
Contributor

@joekaufmanexpensify joekaufmanexpensify left a comment

Choose a reason for hiding this comment

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

WN project 👍

@jnowakow
Copy link
Contributor

@jnowakow has been working on updates to that flow

I think it needs this PR

@DylanDylann
Copy link
Contributor

@mhawryluk Could you please check the failed perf tests?

@DylanDylann
Copy link
Contributor

The offline indicator floats to the middle of the page when navigating away from the default rate form.

Screen.Recording.2026-01-29.at.17.50.35.mov

This is another flow where I don't see this bug happened

Screen.Recording.2026-01-29.at.17.51.09.mov

@mhawryluk
Copy link
Contributor Author

@mhawryluk Could you please check the failed perf tests?

merging main fixed it

@mhawryluk
Copy link
Contributor Author

The offline indicator floats to the middle of the page when navigating away from the default rate form.

should be fixed now. I disabled shouldEnableMaxHeight for this component's ScreenWrapper

@DylanDylann
Copy link
Contributor

DylanDylann commented Jan 29, 2026

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
    • MacOS: Desktop
  • 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
Screen.Recording.2026-01-29.at.21.32.02.mov
Android: mWeb Chrome
Screen.Recording.2026-01-29.at.19.07.31.mov
iOS: HybridApp
Screen.Recording.2026-01-29.at.18.54.37.mov
iOS: mWeb Safari
Screen.Recording.2026-01-29.at.18.53.49.mov
MacOS: Chrome / Safari
Screen.Recording.2026-01-29.at.17.30.03.mov

@DylanDylann
Copy link
Contributor

Checking again ....

@github-actions
Copy link
Contributor

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

Copy link
Contributor

@grgia grgia left a comment

Choose a reason for hiding this comment

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

@mhawryluk we should require upgrade for Time, the same as per Diem

Bug:

Screen.Recording.2026-01-29.at.1.30.35.PM.mov

Otherwise main flows LGTM:

Screen.Recording.2026-01-29.at.1.26.53.PM.mov

@grgia
Copy link
Contributor

grgia commented Jan 29, 2026

image

cc @Expensify/design @dylanexpensify can you confirm if we need this page for time tracking? it's collect or control

@mhawryluk if changes are req, we can tackle in a follow up as this is under beta

@grgia
Copy link
Contributor

grgia commented Jan 29, 2026

fixed tags

@mhawryluk
Copy link
Contributor Author

yeah, I implemented it to be available for both control and collect workspaces, per the design doc, but if we want to limit it to just control we can do that in a follow up!

@grgia
Copy link
Contributor

grgia commented Jan 29, 2026

Thanks @mhawryluk, then we're good to go

Copy link
Contributor

@grgia grgia left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Contributor

@DylanDylann DylanDylann left a comment

Choose a reason for hiding this comment

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

LGTM

@melvin-bot melvin-bot bot requested a review from grgia January 29, 2026 14:33
@grgia grgia merged commit e2ff5f7 into Expensify:main Jan 29, 2026
34 checks passed
@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/grgia in version: 9.3.11-16 🚀

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

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.

9 participants