Skip to content

fix: task assignee resolution for composer short mentions#96500

Merged
mountiny merged 2 commits into
Expensify:mainfrom
callstack-internal:fix/task-short-mention-assignee
Jul 21, 2026
Merged

fix: task assignee resolution for composer short mentions#96500
mountiny merged 2 commits into
Expensify:mainfrom
callstack-internal:fix/task-short-mention-assignee

Conversation

@adhorodyski

@adhorodyski adhorodyski commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Creating a task with a short mention ([] @name Task title) has not assigned the task since July 2025 (4688d4e). The composer passed bare usernames (name) into addDomainToShortMention, which checks full logins (name@domain.com). This check never matched, so the task was created unassigned with @name left in the title.

The fix feeds addDomainToShortMention the full logins list, via a new getAllPersonalDetailLogins() in PersonalDetailsUtils, and looks up the assignee with the existing getPersonalDetailByEmail.

Both reads happen at submit time, so the composer input and send button no longer subscribe to the personal details collection on render.

Fixed Issues

$ #96612
PROPOSAL:

Tests

  1. Sign in with an account on a private email domain that shares the domain with a coworker (e.g. you@company.com and coworker@company.com).
  2. In any report, send [] @coworker Some task (short mention, without the domain).
  3. Verify the task "Some task" is created and assigned to the coworker.
  4. Send [] @nosuchuser Some task and verify the task is created unassigned, titled @nosuchuser Some task.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests. Task creation is optimistic and works offline.

QA Steps

Same as tests.

  • 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

@codecov

codecov Bot commented Jul 20, 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/libs/PersonalDetailsUtils.ts 77.64% <100.00%> (+0.36%) ⬆️
src/libs/ReportUtils.ts 86.14% <ø> (-0.09%) ⬇️
...ox/report/ReportActionCompose/useComposerSubmit.ts 68.75% <100.00%> (+32.38%) ⬆️
... and 119 files with indirect coverage changes

@adhorodyski
adhorodyski force-pushed the fix/task-short-mention-assignee branch from adeba98 to 837aac2 Compare July 20, 2026 16:44
@adhorodyski adhorodyski changed the title Fix task assignee resolution for composer short mentions fix: task assignee resolution for composer short mentions Jul 20, 2026
@adhorodyski
adhorodyski force-pushed the fix/task-short-mention-assignee branch from 837aac2 to b3e0ee8 Compare July 20, 2026 16:53
@adhorodyski

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: b3e0ee8438

ℹ️ 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".

Since 4688d4e the composer passed useShortMentionsList's bare
usernames into addDomainToShortMention, which checks full logins - the
membership test could never match, so `[] @name Task title` created an
unassigned task with the mention prefixed to the title. Feed the
canonical addDomainToShortMention the full logins list from
PersonalDetailsUtils instead and drop the personal-details render
subscriptions from useComposerSubmit.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@adhorodyski
adhorodyski force-pushed the fix/task-short-mention-assignee branch from b3e0ee8 to 1268d18 Compare July 21, 2026 08:05
@adhorodyski
adhorodyski marked this pull request as ready for review July 21, 2026 10:05
@adhorodyski
adhorodyski requested review from a team as code owners July 21, 2026 10:05
@melvin-bot
melvin-bot Bot requested review from marcochavezf and trjExpensify and removed request for a team July 21, 2026 10:06
@melvin-bot

melvin-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

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

Comment thread src/libs/PersonalDetailsUtils.ts
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@ZhenjaHorbach

ZhenjaHorbach commented Jul 21, 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 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
    • 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
    • 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 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
2026-07-21.15.44.00.mov
Android: mWeb Chrome
2026-07-21.15.34.17.mov
iOS: HybridApp
2026-07-21.15.44.00.mov
iOS: mWeb Safari
2026-07-21.15.34.17.mov
MacOS: Chrome / Safari
2026-07-21.15.24.34.mov

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

LGTM!

@mountiny
mountiny merged commit 01aa0c7 into Expensify:main Jul 21, 2026
35 of 36 checks passed
@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.

@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.42-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review: no changes required.

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

This is a bug fix that restores assignee resolution for the composer task shorthand ([] @name Task title) — it feeds addDomainToShortMention the full personal-detail logins and resolves the assignee via getPersonalDetailByEmail. The change is purely internal logic; it introduces no new feature and changes no documented UI flow, feature name, tab, label, or button.

The only task help article, Assign-Tasks.md, documents task creation solely via the + button → Assign a Task flow. The [] @name composer shorthand is not documented anywhere in docs/articles, so nothing in the current help site becomes inaccurate as a result of this fix.

Since no documented behavior changed, I did not create a draft docs PR.

@adhorodyski, if you'd like the [] @name Task title shorthand to be documented as a first-class way to create and assign tasks, let me know and I'll draft an article update for it.

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