Skip to content

[NoQA] [HR Import] Show "Complete Setup" GBR in Workspaces tab icon#93591

Merged
luacmartins merged 10 commits into
Expensify:mainfrom
software-mansion-labs:merge-hr/complete-setup-tab-gbr
Jun 18, 2026
Merged

[NoQA] [HR Import] Show "Complete Setup" GBR in Workspaces tab icon#93591
luacmartins merged 10 commits into
Expensify:mainfrom
software-mansion-labs:merge-hr/complete-setup-tab-gbr

Conversation

@mhawryluk

@mhawryluk mhawryluk commented Jun 15, 2026

Copy link
Copy Markdown
Member

Explanation of Change

Shows a green dot in the LHN/tab bar Workspaces button when there is a workspace with Merge HR "complete setup" state and there are no workspaces with errors.

Fixed Issues

$ #93445
PROPOSAL: N/A

Tests

  1. Make sure you have the mergeHRConnections beta enabled.
  2. Open a workspace, enable HR in More features, go to the HR tab.
  3. Connect a Merge HR provider (Bamboo/Workday/HiBob).
  4. Wait for the first sync to end, until the "Complete setup" link appears.
  5. Verify that when there is a GBR in the provider card, HR tab, workspace row in Workspaces list, there is now also a green dot in the Workspaces tab icon in the navigation tab bar.
  6. Verify that when there is a workspace with RBR, the dot in the navigation tab bar is red, even when there is a workspace with GBR, because errors take precedence over infos.

Offline tests

N/A

QA Steps

N/A

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 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 Zrzut ekranu 2026-06-16 o 14 40 38
Android: mWeb Chrome
iOS: Native Simulator Screenshot - iPhone 17 Pro - 2026-06-16 at 14 32 53
iOS: mWeb Safari
MacOS: Chrome / Safari Zrzut ekranu 2026-06-16 o 11 22 49 Zrzut ekranu 2026-06-16 o 13 10 58

@jmusial jmusial 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.

Couple nits, but overall LGTM 🚀

Comment thread src/hooks/usePolicyIndicatorChecks.ts Outdated
Comment thread src/hooks/useWorkspacesTabIndicatorStatus.ts
@mhawryluk
mhawryluk marked this pull request as ready for review June 16, 2026 13:29
@mhawryluk
mhawryluk requested review from a team as code owners June 16, 2026 13:29
@melvin-bot
melvin-bot Bot requested review from ZhenjaHorbach and flaviadefaria and removed request for a team June 16, 2026 13:29
@melvin-bot

melvin-bot Bot commented Jun 16, 2026

Copy link
Copy Markdown

@ZhenjaHorbach 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 June 16, 2026 13:29
@mhawryluk

Copy link
Copy Markdown
Member Author

cc: @bernhardoj @ikevin127 (Merge HR project)

@ikevin127

ikevin127 commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

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 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 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 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)
  • 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.
  • 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

HR [GBR] HR [GBR] - Workspaces List HR [RBR] HR [RBR] - Workspaces List
hr-gbr-dev ht-gbr-wslist hr-rbr-dev ht-rbr-wslist

@ikevin127 ikevin127 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.

🟢 LGTM

This [NoQA] PR adds a green indicator dot to the Workspaces tab when a policy has Merge HR in "complete setup" state (sync done, groups available, but setup not completed). It also refactors usePolicyIndicatorChecks to cleanly separate error (red) from info (green) policy statuses ✅

@melvin-bot

melvin-bot Bot commented Jun 17, 2026

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #93445 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot
melvin-bot Bot requested a review from luacmartins June 17, 2026 00:28
@twisterdotcom

Copy link
Copy Markdown
Contributor

@grgia can probably help review this tomorrow instead @luacmartins

@twisterdotcom
twisterdotcom requested a review from grgia June 17, 2026 00:36
luacmartins
luacmartins previously approved these changes Jun 17, 2026
const {policyErrorStatus, domainStatus, policyIDWithErrors} = usePolicyIndicatorChecks();

const errorStatus = accountStatus ?? policyStatus ?? domainStatus;
const errorStatus = accountStatus ?? policyErrorStatus ?? domainStatus;

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.

Do we no longer need the policyInfoStatus fallback?

@grgia grgia Jun 17, 2026

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.

@mhawryluk ill hold merge on this, idk the answer

@mhawryluk mhawryluk Jun 18, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

useIndicatorStatus is used for the Debug Mode banner in the navigation tab bar. in this PR I only updated useWorkspacesTabIndicatorStatus as this is the one responsible for the dot in the workspace tab icon. so currently the new info status is not included in the debug mode thing. but maybe we should update it for consistency? since we include Account info status there already, though not all statuses are actually presented, cause some lack a configured message in getSettingsMessage. so if we wanted to include "Complete setup" in the debug mode tab view, I would also need a copy for the message, something like "HR integration requires setup" maybe? @grgia @twisterdotcom

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Zrzut ekranu 2026-06-18 o 10 33 13

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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Implemented the debug mode support. An actual, nonhypothetical screenshot below.

Zrzut ekranu 2026-06-18 o 16 30 16

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

there is an issue with navigation when clicking the View button from a different workspace to navigate to another one, the left part of the split does not get updated in the wide view. but this is an existing bug reproducable on staging

Nagranie.z.ekranu.2026-06-18.o.17.24.51.mov
Nagranie.z.ekranu.2026-06-18.o.17.15.06.mov

grgia
grgia previously approved these changes Jun 17, 2026
@mhawryluk
mhawryluk dismissed stale reviews from grgia and luacmartins via fbb7fdc June 18, 2026 14:10
@melvin-bot

melvin-bot Bot commented Jun 18, 2026

Copy link
Copy Markdown

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
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 d600b72d4e7..bca80bd2169 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -9555,6 +9555,7 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
             theresAProblemWithYourWallet: 'Es gibt ein Problem mit deinem Wallet',
             theresAProblemWithYourWalletTerms: 'Es gibt ein Problem mit deinen Wallet-Bedingungen',
             aBankAccountIsLocked: 'Ein Bankkonto ist gesperrt',
+            completeHrSetup: 'HR-Einrichtung abschließen',
         },
     },
     emptySearchView: {
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 31e9b699cab..5e73b9358c0 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -9712,6 +9712,7 @@ ${amount} para ${merchant} - ${date}`,
             theresAProblemWithYourWallet: 'Hay un problema con tu billetera',
             theresAProblemWithYourWalletTerms: 'Hay un problema con los términos de tu billetera',
             aBankAccountIsLocked: 'Una cuenta bancaria está bloqueada',
+            completeHrSetup: 'Completa la configuración de RR. HH.',
         },
     },
     emptySearchView: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index d764be15a28..931fecb6f06 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -9587,6 +9587,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
             theresAProblemWithYourWallet: 'Il y a un problème avec votre portefeuille',
             theresAProblemWithYourWalletTerms: 'Il y a un problème avec les conditions de votre portefeuille',
             aBankAccountIsLocked: 'Un compte bancaire est verrouillé',
+            completeHrSetup: 'Terminer la configuration RH',
         },
     },
     emptySearchView: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index f1240aee0d7..f91f5d6e65f 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -9543,6 +9543,7 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
             theresAProblemWithYourWallet: 'Si è verificato un problema con il tuo portafoglio',
             theresAProblemWithYourWalletTerms: 'C’è un problema con i termini del tuo portafoglio',
             aBankAccountIsLocked: 'Un conto bancario è bloccato',
+            completeHrSetup: 'Completa la configurazione HR',
         },
     },
     emptySearchView: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index f5e6745882f..37240f1f219 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -9422,6 +9422,7 @@ ${reportName}`,
             theresAProblemWithYourWallet: 'ウォレットに問題があります',
             theresAProblemWithYourWalletTerms: 'ウォレットの利用規約に問題があります',
             aBankAccountIsLocked: '銀行口座がロックされています',
+            completeHrSetup: '人事設定を完了する',
         },
     },
     emptySearchView: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 01764358e9b..e495cac0f2a 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -9509,6 +9509,7 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
             theresAProblemWithYourWallet: 'Er is een probleem met je wallet',
             theresAProblemWithYourWalletTerms: 'Er is een probleem met de voorwaarden van je wallet',
             aBankAccountIsLocked: 'Een bankrekening is geblokkeerd',
+            completeHrSetup: 'HR-configuratie voltooien',
         },
     },
     emptySearchView: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index aeefb8e21a0..ebddb2a6ac6 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -9495,6 +9495,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             theresAProblemWithYourWallet: 'Wystąpił problem z Twoim portfelem',
             theresAProblemWithYourWalletTerms: 'Wystąpił problem z warunkami Twojego portfela',
             aBankAccountIsLocked: 'Konto bankowe jest zablokowane',
+            completeHrSetup: 'Dokończ konfigurację HR',
         },
     },
     emptySearchView: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 85a71c0b595..e9bca36936f 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -9499,6 +9499,7 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
             theresAProblemWithYourWallet: 'Há um problema com sua carteira',
             theresAProblemWithYourWalletTerms: 'Há um problema com os termos da sua carteira',
             aBankAccountIsLocked: 'Uma conta bancária está bloqueada',
+            completeHrSetup: 'Concluir configuração de RH',
         },
     },
     emptySearchView: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 967b91f9938..5c1eb07f667 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -9246,6 +9246,7 @@ ${reportName}`,
             theresAProblemWithYourWallet: '您的钱包出现问题',
             theresAProblemWithYourWalletTerms: '您的钱包条款存在问题',
             aBankAccountIsLocked: '银行账户已锁定',
+            completeHrSetup: '完成人力资源设置',
         },
     },
     emptySearchView: {

Note

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

View workflow run

@mhawryluk

Copy link
Copy Markdown
Member Author

@codex review

@codecov

codecov Bot commented Jun 18, 2026

Copy link
Copy Markdown

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/CONST/index.ts 93.84% <ø> (ø)
src/hooks/useIndicatorStatus.ts 100.00% <100.00%> (ø)
src/hooks/usePolicyIndicatorChecks.ts 100.00% <100.00%> (ø)
src/hooks/useWorkspacesTabIndicatorStatus.ts 100.00% <100.00%> (ø)
src/components/Navigation/DebugTabView.tsx 49.62% <9.09%> (-1.52%) ⬇️
... and 20 files with indirect coverage changes

@luacmartins

Copy link
Copy Markdown
Contributor

@ikevin127 can you please update the checklist to the new template https://raw.githubusercontent.com/Expensify/App/main/contributingGuides/REVIEWER_CHECKLIST.md?

@ikevin127

Copy link
Copy Markdown
Contributor

@luacmartins Done, updated the checklist with new screenshots that show the latest updates + dev mode activated.

🟢 LGTM

@luacmartins

Copy link
Copy Markdown
Contributor

@ikevin127 it seems like the checklist is still outdated (it has 59 items, instead of the 50 items on the new checklist). Can you update it to this template? https://raw.githubusercontent.com/Expensify/App/main/contributingGuides/REVIEWER_CHECKLIST.md

@melvin-bot
melvin-bot Bot requested a review from luacmartins June 18, 2026 22:57
@luacmartins

Copy link
Copy Markdown
Contributor

Merging since @grgia had already approved

@luacmartins
luacmartins merged commit fcc6f37 into Expensify:main Jun 18, 2026
35 of 39 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @luacmartins 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/luacmartins in version: 9.4.16-1 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 No help site changes are required.

I reviewed the changes in this PR against the help site articles under App/docs/articles.

This is a [NoQA] UI-only change: it adds a green-dot (GBR) indicator to the Workspaces tab icon in the navigation bar when a workspace is in the Merge HR "Complete setup" state and no workspaces have errors. The logic lives entirely in the indicator hooks (useIndicatorStatus, usePolicyIndicatorChecks, useWorkspacesTabIndicatorStatus) plus localized debug copy.

Why no docs update is needed:

  • The help site documents product features and how-to flows — it does not document the navigation tab-icon indicator dots (GBR/RBR). There is no existing article describing this behavior to update.
  • There is no New Expensify help article for the Merge HR / HRIS connection flow (Bamboo/Workday/HiBob) that references a "Complete setup" step, so there's nothing to keep in sync.
  • The only user-facing copy added (Complete HR setup) is a debug-only indicator label, not customer-facing help content.

Because no changes are required, I did not open a draft help site PR.

@mhawryluk, if you believe a customer-facing help article should exist for the Merge HR connection flow (separate from this indicator change), let me know and I can draft one.

Comment on lines -2037 to +2036
"../../tests/unit/usePolicyIndicatorChecksTest.ts" "@typescript-eslint/no-unsafe-type-assertion" 11
"../../tests/unit/usePolicyIndicatorChecksTest.ts" "@typescript-eslint/no-unsafe-type-assertion" 14

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.

Please don't increase instances of this. Use partial object types instead.

Comment on lines -2051 to +2050
"../../tests/unit/useWorkspacesTabIndicatorStatusTest.ts" "@typescript-eslint/no-unsafe-type-assertion" 5
"../../tests/unit/useWorkspacesTabIndicatorStatusTest.ts" "@typescript-eslint/no-unsafe-type-assertion" 6

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.

Same here.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.4.16-5 🚀

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