You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[hold for BZ checklist] [Due for payment 2026-01-15] [$250] Unable to Tag User by Display Name (e.g. “@al”) in New Expensify #71836
Version Number: 9.2.21-2 Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@roryabraham Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Enter a workspace that includes @al (al@test.com), or invite him to one
Select Al from the mention-user popup using keyboard or mouse
Expected Result:
User Al should be correctly tagged after selection from the mention popup.
Actual Result:
No tag is inserted when selecting Al from the mention list, Tag only works if user manually types the full email (@al@test.com) and then presses space.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
changed the title [-]Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/-][+][$250] Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/+]on Oct 6, 2025
changed the title [-][Due for payment 2026-01-15] [$250] Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/-][+][`hold for BZ checklist`] [Due for payment 2026-01-15] [$250] Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/+]on Jan 15, 2026
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Rather than a bug, it'a an improvement on the existing behavior. Short-mentions are handled by ExpensiMark parser where the minimum number of characters for mention was set to 3. and hence any short-mention with 2 or less characters could not be highlighted.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
User has a private domain workspace member with 1 or 2 char short-mention name.(add someone who has only 1 or 2 character prefix to their private domain email ( x@private.domain or av@private.domain))
Test:
Open workspace chat.
Type '@' and then select 1,2 char mention from suggestions.
Activity
melvin-bot commentedon Oct 3, 2025
Triggered auto assignment to @clarajones-expensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.MelvinBot commentedon Oct 3, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
clarajones-expensify commentedon Oct 6, 2025
I'm able to repro using the steps in the OP
[-]Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/-][+][$250] Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/+]melvin-bot commentedon Oct 6, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021975224128872718970
103 remaining items
clarajones-expensify commentedon Jan 14, 2026
Hi @sobitneupane ! Do we need a BZ checklist here? thanks!
clarajones-expensify commentedon Jan 15, 2026
Payment Summary
Contributor: @ChavdaSachin paid $250 via automatic offer
Contributor+: @sobitneupane due $250 via NewDot
[-][Due for payment 2026-01-15] [$250] Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/-][+][`hold for BZ checklist`] [Due for payment 2026-01-15] [$250] Unable to Tag User by Display Name (e.g. “@al”) in New Expensify[/+]melvin-bot commentedon Jan 19, 2026
@stitesExpensify Eep! 4 days overdue now. Issues have feelings too...
clarajones-expensify commentedon Jan 23, 2026
posted in contributor plus channel
melvin-bot commentedon Jan 23, 2026
@stitesExpensify Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
sobitneupane commentedon Jan 26, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Rather than a bug, it'a an improvement on the existing behavior. Short-mentions are handled by
ExpensiMarkparser where the minimum number of characters for mention was set to 3. and hence any short-mention with 2 or less characters could not be highlighted.[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Zapier Logs
Run ID: 00040eee-63fb-ae1b-4e2d-cd78072480c4sobitneupane commentedon Jan 26, 2026
Regression Test Proposal
Precondition:
x@private.domainorav@private.domain))Test:
Do we agree 👍 or 👎
stitesExpensify commentedon Jan 26, 2026
Not overdue
clarajones-expensify commentedon Jan 27, 2026
Payment Summary here
garrettmknight commentedon Mar 16, 2026
$250 approved for @sobitneupane