Skip to content

Add Task action badge for chats with outstanding task reports#91552

Merged
danieldoglas merged 3 commits into
mainfrom
claude-addTaskActionBadge
May 25, 2026
Merged

Add Task action badge for chats with outstanding task reports#91552
danieldoglas merged 3 commits into
mainfrom
claude-addTaskActionBadge

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

@MelvinBot MelvinBot commented May 25, 2026

Explanation of Change

When a workspace chat has an outstanding task report assigned to the current user, the LHN now displays a green "Task" action badge — matching the behavior of the existing Pay, Approve, Submit, and Fix badges.

The existing code already detected outstanding tasks via getActionTypeForAssigneeToComplete and set requiresAttention (green dot), but never returned an actionBadge for the task case. This change adds a TASK badge type and returns it when the assignee action is a task.

Fixed Issues

$ #91523

Tests

  • Verify that no errors appear in the JS console
  • Open a workspace chat that has an outstanding (incomplete) task assigned to you
  • Verify a green "Task" badge appears next to the chat in the LHN
  • Complete the task
  • Verify the "Task" badge disappears from the LHN
  • Open a workspace chat that has an outstanding expense report (e.g. needing approval or payment)
  • Verify the existing expense badges (Pay, Approve, Submit, Fix) still appear correctly and are not affected

Offline tests

  • Disconnect from the network
  • Verify the "Task" badge remains visible on chats that had outstanding tasks before going offline
  • Reconnect and verify the badge state updates correctly

QA Steps

  • Open a workspace chat that has an outstanding (incomplete) task assigned to you
  • Verify a green "Task" badge appears next to the chat in the LHN
  • Complete the task and verify the badge disappears
  • Verify existing expense badges (Pay, Approve, Submit, Fix) are unaffected
  • 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 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Show a green 'Task' badge in the LHN for workspace chats that have an
outstanding task report assigned to the current user. This follows the
same pattern as the existing Pay, Approve, Submit, and Fix badges.

Co-authored-by: Aimane Chnaif <aimane-chnaif@users.noreply.github.com>
@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 5c96b1c40b1..0691802e125 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: 'Startseite',
         inbox: 'Posteingang',
         yourReviewIsRequired: 'Ihre Überprüfung ist erforderlich',
-        actionBadge: {
-            submit: 'Senden',
-            approve: 'Genehmigen',
-            pay: 'Bezahlen',
-            fix: 'Beheben',
-            task: 'Aufgabe',
-        },
+        actionBadge: {submit: 'Senden', approve: 'Genehmigen', pay: 'Bezahlen', fix: 'Beheben', task: 'Aufgabe'},
         success: 'Erfolgreich',
         group: 'Gruppe',
         profile: 'Profil',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index c7252bd7a76..a98c2695169 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -73,13 +73,7 @@ const translations: TranslationDeepObject<typeof en> = {
         workspaces: 'Espacios de trabajo',
         inbox: 'Recibidos',
         yourReviewIsRequired: 'Se requiere tu revisión',
-        actionBadge: {
-            submit: 'Enviar',
-            approve: 'Aprobar',
-            pay: 'Pagar',
-            fix: 'Corregir',
-            task: 'Tarea',
-        },
+        actionBadge: {submit: 'Enviar', approve: 'Aprobar', pay: 'Pagar', fix: 'Corregir', task: 'Tarea'},
         home: 'Inicio',
         group: 'Grupo',
         profile: 'Perfil',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 8fcaf47b1a5..5bd9908c913 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: 'Accueil',
         inbox: 'Boîte de réception',
         yourReviewIsRequired: 'Votre révision est requise',
-        actionBadge: {
-            submit: 'Soumettre',
-            approve: 'Approuver',
-            pay: 'Payer',
-            fix: 'Corriger',
-            task: 'Tâche',
-        },
+        actionBadge: {submit: 'Soumettre', approve: 'Approuver', pay: 'Payer', fix: 'Corriger', task: 'Tâche'},
         success: 'Réussi',
         group: 'Groupe',
         profile: 'Profil',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 0110e547fd6..6bdea3b4345 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: 'Home',
         inbox: 'Posta in arrivo',
         yourReviewIsRequired: 'È richiesta la tua revisione',
-        actionBadge: {
-            submit: 'Invia',
-            approve: 'Approva',
-            pay: 'Paga',
-            fix: 'Correggi',
-            task: 'Attività',
-        },
+        actionBadge: {submit: 'Invia', approve: 'Approva', pay: 'Paga', fix: 'Correggi', task: 'Attività'},
         success: 'Operazione riuscita',
         group: 'Gruppo',
         profile: 'Profilo',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 1cb6d901a73..96787669842 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: 'ホーム',
         inbox: '受信トレイ',
         yourReviewIsRequired: '確認が必要です',
-        actionBadge: {
-            submit: '送信',
-            approve: '承認する',
-            pay: '支払う',
-            fix: '修正',
-            task: 'タスク',
-        },
+        actionBadge: {submit: '送信', approve: '承認する', pay: '支払う', fix: '修正', task: 'タスク'},
         success: '成功しました',
         group: 'グループ',
         profile: 'プロフィール',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 64e92434438..a97638a5cb4 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: 'Home',
         inbox: 'Inbox',
         yourReviewIsRequired: 'Uw beoordeling is vereist',
-        actionBadge: {
-            submit: 'Verzenden',
-            approve: 'Goedkeuren',
-            pay: 'Betalen',
-            fix: 'Oplossen',
-            task: 'Taak',
-        },
+        actionBadge: {submit: 'Verzenden', approve: 'Goedkeuren', pay: 'Betalen', fix: 'Oplossen', task: 'Taak'},
         success: 'Gelukt',
         group: 'Groep',
         profile: 'Profiel',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index f68a907533b..28c9415a400 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: 'Strona główna',
         inbox: 'Skrzynka odbiorcza',
         yourReviewIsRequired: 'Wymagana jest Twoja weryfikacja',
-        actionBadge: {
-            submit: 'Wyślij',
-            approve: 'Zatwierdź',
-            pay: 'Zapłać',
-            fix: 'Napraw',
-            task: 'Zadanie',
-        },
+        actionBadge: {submit: 'Wyślij', approve: 'Zatwierdź', pay: 'Zapłać', fix: 'Napraw', task: 'Zadanie'},
         success: 'Sukces',
         group: 'Grupa',
         profile: 'Profil',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 958e6e07c76..18a4e0653dc 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: 'Início',
         inbox: 'Caixa de entrada',
         yourReviewIsRequired: 'Sua revisão é necessária',
-        actionBadge: {
-            submit: 'Enviar',
-            approve: 'Aprovar',
-            pay: 'Pagar',
-            fix: 'Corrigir',
-            task: 'Tarefa',
-        },
+        actionBadge: {submit: 'Enviar', approve: 'Aprovar', pay: 'Pagar', fix: 'Corrigir', task: 'Tarefa'},
         success: 'Concluído',
         group: 'Grupo',
         profile: 'Perfil',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index ab5abd15649..e3a3bd9089a 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -119,13 +119,7 @@ const translations: TranslationDeepObject<typeof en> = {
         home: '主页',
         inbox: '收件箱',
         yourReviewIsRequired: '需要您的审核',
-        actionBadge: {
-            submit: '提交',
-            approve: '批准',
-            pay: '支付',
-            fix: '修复',
-            task: '任务',
-        },
+        actionBadge: {submit: '提交', approve: '批准', pay: '支付', fix: '修复', task: '任务'},
         success: '成功',
         group: '群组',
         profile: '个人资料',

Note

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

View workflow run

Comment thread src/libs/ReportUtils.ts Outdated
Comment on lines +4240 to +4245
const isAssigneeExpenseAction = actionTypeForAssigneeToComplete === CONST.REPORT.ACTION_TYPES_FOR_ASSIGNEE_TO_COMPLETE.EXPENSE;
const isAssigneeTaskAction = actionTypeForAssigneeToComplete === CONST.REPORT.ACTION_TYPES_FOR_ASSIGNEE_TO_COMPLETE.TASK;
const expenseBadge = isAssigneeExpenseAction
? getBadgeFromIOUReport(optionOrReport, undefined, policy, optionReportMetadata, invoiceReceiverPolicy, currentUserLogin, currentUserAccountID)
: undefined;
const assigneeBadge = expenseBadge ?? (isAssigneeTaskAction ? CONST.REPORT.ACTION_BADGE.TASK : undefined);
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.

@MelvinBot simplify this code if possible.
If actionTypeForAssigneeToComplete exists, it's either EXPENSE or TASK.
So if !isAssigneeExpenseAction, it always means TASK action.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good call! Simplified — removed isAssigneeTaskAction and expenseBadge, and replaced with a single ternary: if it's an expense action, get the expense badge; otherwise it's always TASK. Pushed in 9371562.

The new TASK action badge replaces the GBR green dot for reports
with outstanding child tasks. Updated two tests to check for the
Task badge text instead of the GBR Icon testID.

Co-authored-by: Aimane Chnaif <aimane-chnaif@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing test (job 3) check: two tests in tests/ui/LHNItemsPresence.tsx expected a GBR Icon testID, but the new TASK action badge replaces the GBR green dot for outstanding child tasks. Updated both tests to assert on the Task badge text instead.

Since actionTypeForAssigneeToComplete is either EXPENSE or TASK,
remove the redundant isAssigneeTaskAction check and use a simple
ternary instead.

Co-authored-by: Aimane Chnaif <aimane-chnaif@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

The Jest test failure was already fixed in commit 66f83d9 — the two tests in LHNItemsPresence.tsx were updated to check for the "Task" badge text instead of the old GBR Icon testID. The latest CI run includes this fix and is currently in progress. No additional changes needed.

@aimane-chnaif
Copy link
Copy Markdown
Contributor

@MelvinBot add test steps and check off all items. They're verified.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Code Review

The core logic is correct and clean. Two observations worth considering:

1. reportAction filter always selects task actions, even on the expense path

ReportUtils.ts:4246-4249 filters for childType === CONST.REPORT.TYPE.TASK regardless of whether isAssigneeExpenseAction is true. So when the assignee action is an expense, the returned reportAction is still the first incomplete task, not the expense action. This pre-dates the PR but is a latent bug — the caller may use reportAction expecting it to correspond to the expense.

2. Everything else looks good

  • ACTION_TYPES_FOR_ASSIGNEE_TO_COMPLETE only has EXPENSE and TASK — the ternary simplification is valid
  • TASK badge is properly defined in CONST, translated in all locale files, and rendered correctly by InfoBadge.tsx
  • When getBadgeFromIOUReport returns undefined (non-reimbursable expenses), the spread pattern correctly omits actionBadge, falling back to the GBR dot icon
  • Test assertions using getByText('Task') are consistent with how the test suite works (English locale default)

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Done — added test steps for Tests, Offline tests, and QA Steps sections, and checked off all checklist items.

@aimane-chnaif
Copy link
Copy Markdown
Contributor

@MelvinBot mark as ready for review

@MelvinBot MelvinBot marked this pull request as ready for review May 25, 2026 01:22
@MelvinBot MelvinBot requested a review from a team as a code owner May 25, 2026 01:22
@melvin-bot melvin-bot Bot requested a review from aimane-chnaif May 25, 2026 01:22
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Marked as ready for review! ✅

@melvin-bot melvin-bot Bot requested review from JmillsExpensify and removed request for a team May 25, 2026 01:22
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 25, 2026

@aimane-chnaif 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 May 25, 2026 01:22
@aimane-chnaif
Copy link
Copy Markdown
Contributor

aimane-chnaif commented May 25, 2026

While testing, I discovered bug happening on production. Out of scope.

Repro step:

  1. Create task 1 and assign me
  2. Create an expense
  3. Create task 2 and assign me
  4. Observe that LHN badge is 🟢 (In this PR, Task)
  5. Mark task 1 as complete

Expected Result:
LHN badge changes to Submit

Actual Result:
LHN badge briefly changes to Submit and back to 🟢 (In this PR, Task)

bug.mov

@aimane-chnaif
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
    • 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
android.mov
Android: mWeb Chrome
iOS: HybridApp
ios.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
web.mov

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 25, 2026

We did not find an internal engineer to review this PR, trying to assign a random engineer to #91523 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 danieldoglas May 25, 2026 01:37
@danieldoglas danieldoglas merged commit b17de2b into main May 25, 2026
54 of 56 checks passed
@danieldoglas danieldoglas deleted the claude-addTaskActionBadge branch May 25, 2026 20:53
@github-actions
Copy link
Copy Markdown
Contributor

🚧 @danieldoglas 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/danieldoglas in version: 9.3.82-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Yes, help site changes are needed. This PR adds a new green Task action badge in the LHN, which is user-facing behavior not currently documented.

I've created a draft docs PR: #91656

Changes made:

  • Updated docs/articles/new-expensify/chat/Assign-Tasks.md to add a new section explaining the green Task badge that appears in the LHN when a user has an outstanding task assigned to them, and how it disappears upon task completion.

@aimane-chnaif, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@mitarachim
Copy link
Copy Markdown

Deploy Blocker #91664 was identified to be related to this PR.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.82-3 🚀

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.

5 participants