Skip to content

Add EducationalTooltip for Unread Tab. - #99840

Merged
JS00001 merged 14 commits into
Expensify:mainfrom
hungvu193:feat-99810
Sep 14, 2026
Merged

JS00001 merged 14 commits into
Expensify:mainfrom
hungvu193:feat-99810

Conversation

@hungvu193

@hungvu193 hungvu193 commented Aug 30, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

As the PR title, in this PR we add the Educational Tooltip for Inbox Unread Tab, with the following requirements:

When someone views the Inbox and has at least one unread message older than 3 months, show the existing educational tooltip pointing at the Inbox tabs, promoting "Mark all as read".

  1. Show it at most once every 7 days per account.
  2. Dismissable and store the last-shown timestamp so the weekly cap survives reloads.

Fixed Issues

$ #99810
PROPOSAL: N/A

Tests

Same as QA steps

  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  1. Login with any account that has 3 month olds unread message.
  2. Verify that the EducationalTooltip appears under the unread tab.
  3. Verify that you can close it.
  4. Reload the page after you close it.
  5. Verify that it won't appear again.
  • Verify that no errors appear in the JS console

PR Author Checklist

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

Screenshots/Videos

Android: Native Screenshot 2026-08-30 at 18 30 52
Screen.Recording.2026-08-30.at.18.29.12.mov
Android: mWeb Chrome
Screen.Recording.2026-08-30.at.18.29.12.mov
iOS: Native
Screen.Recording.2026-08-30.at.18.27.09.mov
iOS: mWeb Safari
Screen.Recording.2026-08-30.at.18.23.04.mov
MacOS: Chrome / Safari
Screen.Recording.2026-08-30.at.16.24.06.mov

@melvin-bot

melvin-bot Bot commented Aug 30, 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 bun ./scripts/generateTranslations.ts --help

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

@codecov

codecov Bot commented Aug 30, 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 91.52% <ø> (ø)
src/components/TabSelector/TabSelectorBase.tsx 89.74% <ø> (ø)
src/components/TabSelector/TabSelectorItem.tsx 100.00% <ø> (ø)
src/hooks/useSidebarOrderedReports.tsx 87.27% <100.00%> (ø)
src/libs/SidebarUtils.ts 90.85% <100.00%> (+0.40%) ⬆️
src/libs/TooltipUtils.ts 100.00% <100.00%> (ø)
src/pages/inbox/sidebar/InboxTabSelector.tsx 81.35% <100.00%> (+2.11%) ⬆️
src/types/onyx/DismissedProductTraining.ts 0.00% <ø> (ø)
src/components/ProductTrainingContext/index.tsx 90.74% <75.00%> (-0.77%) ⬇️
src/components/ProductTrainingContext/TOOLTIPS.ts 31.57% <33.33%> (+0.32%) ⬆️
... and 13 files with indirect coverage changes

@hungvu193
hungvu193 marked this pull request as ready for review August 30, 2026 11:27
@hungvu193
hungvu193 requested review from a team as code owners August 30, 2026 11:27
@melvin-bot
melvin-bot Bot requested review from heyjennahay and truph01 and removed request for a team August 30, 2026 11:27
@melvin-bot

melvin-bot Bot commented Aug 30, 2026

Copy link
Copy Markdown

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

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d60b966fdf

ℹ️ About Codex in GitHub

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

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

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

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

Comment thread src/selectors/Report.ts Resolved
@hungvu193

hungvu193 commented Aug 30, 2026 •

Copy link
Copy Markdown
Contributor Author

@truph01 We need to wait for https://github.com/Expensify/Auth/pull/24116 to be deployed, but in the meantime, you can review the UI logic. The tricky part is the 3 month old check for unread message, you can comment it out:

- const {renderProductTrainingTooltip, shouldShowProductTrainingTooltip} = useProductTrainingContext(CONST.PRODUCT_TRAINING_TOOLTIP_NAMES.MARK_ALL_AS_READ, hasStaleUnreadReport);

+ const {renderProductTrainingTooltip, shouldShowProductTrainingTooltip} = useProductTrainingContext(CONST.PRODUCT_TRAINING_TOOLTIP_NAMES.MARK_ALL_AS_READ);

Comment thread src/hooks/useSidebarOrderedReports.tsx Resolved
Comment thread src/hooks/useSidebarOrderedReports.tsx Resolved
@truph01

truph01 commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: d8973daf34

ℹ️ About Codex in GitHub

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

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

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

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

@hungvu193

Copy link
Copy Markdown
Contributor Author

@truph01 this is ready for your another review 🙇

@hungvu193
hungvu193 requested a review from truph01 September 4, 2026 07:45
@truph01

truph01 commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Bug: The tooltip is still shown when opening other screens:

Screen.Recording.2026-09-07.at.14.22.11.mov

@hungvu193

Copy link
Copy Markdown
Contributor Author

Bug: The tooltip is still shown when opening other screens:

Screen.Recording.2026-09-07.at.14.22.11.mov

Fixed in f3d788f

@truph01

truph01 commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

@hungvu193 With the new fix, the tooltip only appears in small device, but the desktop device.

@melvin-bot

melvin-bot Bot commented Sep 14, 2026

Copy link
Copy Markdown

I could not review this diff, so I did not approve the workflow runs. An Expensify employee will review it and approve them manually.

@hungvu193

Copy link
Copy Markdown
Contributor Author

@truph01 Fixed. Can you verify again 😅 ?

Screen.Recording.2026-09-14.at.12.07.24.mov

@truph01

truph01 commented Sep 14, 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

Android: HybridApp
Screen.Recording.2026-09-14.at.14.17.57.mov
Android: mWeb Chrome
Screen.Recording.2026-09-14.at.14.30.52.mov
iOS: HybridApp
Screen.Recording.2026-09-14.at.14.18.32.mov
iOS: mWeb Safari
Screen.Recording.2026-09-14.at.14.20.50.mov
MacOS: Chrome / Safari
Screen.Recording.2026-09-14.at.14.10.47.mov

@truph01

truph01 commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

@codex review

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 561f93c037

ℹ️ About Codex in GitHub

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

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

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

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

Comment thread src/hooks/useSidebarOrderedReports.tsx Resolved
@melvin-bot

melvin-bot Bot commented Sep 14, 2026

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #99810 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 JS00001 September 14, 2026 10:00

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

@hungvu193 was this NVP name added to the BE?

@hungvu193

Copy link
Copy Markdown
Contributor Author

@hungvu193 was this NVP name added to the BE?

Yes. It was added here (https://github.com/Expensify/Auth/pull/24116 was deployed to prod).

@JS00001

JS00001 commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Nice, ty!

@JS00001
JS00001 merged commit 89355ab into Expensify:main Sep 14, 2026
38 of 42 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 JS00001 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/JS00001 in version: 9.4.78-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

Yes — a help site update is required

Draft PR: #101143 — Docs updates for E/A#99840 Document Mark all as read on Inbox tabs (labelled HelpDot, assigned to MelvinBot).

Why: this PR adds a tooltip on the Unread tab promoting Mark all as read, but the help site never documented that action. docs/articles/new-expensify/getting-started/Navigating-New-Expensify.md:69-85 describes the All, Unread, and To-dos tabs and their count badges, and stops there. A member who sees the tooltip — or dismisses it — has nothing to look up.

What changed (one file, docs-only):

  • New ## How to mark all chats as read from the Inbox tabs section, with separate web (right-click) and mobile (long-press) steps.
  • Documents the tab-dependent scope: All and Unread mark every unread chat as read, To-dos marks only the chats listed in To-dos (InboxTabSelector.tsx:97-99).
  • Notes the tooltip: shows when unread messages are older than three months, dismissable, reappears at most once a week.
  • Three new FAQ entries, plus expanded keywords and internalScope.
UI verification

Verified live on dev NewDot web: the three tab labels read exactly All, Unread, To-dos (confirmed in the accessibility tree).

The menu item, modal title, prompts, and buttons could not be confirmed live — the web automation harness rejects both click --button secondary and longpress with UNSUPPORTED_OPERATION, so the popover never opens. Those strings came from source instead:

  • Menu item / modal title / confirm button: Mark all as read (en.ts:3299)
  • Prompt from All / Unread: Are you sure you want to mark all chats as read? (en.ts:3300)
  • Prompt from To-dos: Are you sure you want to mark all to-do chats as read? (en.ts:3301)
  • Cancel button: Cancel (common.cancel)

Please spot-check those four strings by hand during review.

Three-month threshold: CONST/index.ts INBOX_TAB_STALE_UNREAD_MONTHS: 3. Seven-day reappear window: TOOLTIPS.ts.

What I deliberately did not document

The tooltip copy itself (Right-click to mark all as read. / Long-press to mark all as read.) and its per-account dismissal storage are in-product mechanics, not member workflows, so they don't belong in an article. The behavior the tooltip points at is what I documented.

The ten non-English language files in this PR are translations of that same tooltip string — the help site has no localized equivalent of this article, so no action there.


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

@jponikarchuk

Copy link
Copy Markdown

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

@jponikarchuk

Copy link
Copy Markdown

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.78-3 🚀

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

Bundle Size Analysis (Sentry):

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