Skip to content

[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

Closed

Description

@m-natarajan

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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:

  1. Enter a workspace that includes @al (al@test.com), or invite him to one
  2. In the message composer, type @al
  3. 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:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021975224128872718970
  • Upwork Job ID: 1975224128872718970
  • Last Price Increase: 2025-12-05
  • Automatic offers:
    • ChavdaSachin | Contributor | 109772675
Issue OwnerCurrent Issue Owner: @stitesExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 3, 2025
  2. melvin-bot commented on Oct 3, 2025

    @melvin-bot

    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.

  3. MelvinBot commented on Oct 3, 2025

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  4. clarajones-expensify commented on Oct 6, 2025

    @clarajones-expensify
    Contributor

    I'm able to repro using the steps in the OP

  5. 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
  6. melvin-bot commented on Oct 6, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 6, 2025
  8. 103 remaining items

  9. clarajones-expensify commented on Jan 14, 2026

    @clarajones-expensify
    Contributor

    Hi @sobitneupane ! Do we need a BZ checklist here? thanks!

  10. clarajones-expensify commented on Jan 15, 2026

    @clarajones-expensify
    Contributor

    Payment Summary

    Contributor: @ChavdaSachin paid $250 via automatic offer
    Contributor+: @sobitneupane due $250 via NewDot

  11. 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
  12. melvin-bot commented on Jan 19, 2026

    @melvin-bot

    @stitesExpensify Eep! 4 days overdue now. Issues have feelings too...

  13. clarajones-expensify commented on Jan 23, 2026

    @clarajones-expensify
    Contributor
  14. melvin-bot commented on Jan 23, 2026

    @melvin-bot

    @stitesExpensify Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  15. sobitneupane commented on Jan 26, 2026

    @sobitneupane
    Contributor

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

    Zapier Logs Run ID: 00040eee-63fb-ae1b-4e2d-cd78072480c4
  16. sobitneupane commented on Jan 26, 2026

    @sobitneupane
    Contributor

    Regression Test Proposal

    Precondition:

    • 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:

    1. Open workspace chat.
    2. Type '@' and then select 1,2 char mention from suggestions.
    3. Verify mention is rendered successfully.

    Do we agree 👍 or 👎

  17. stitesExpensify commented on Jan 26, 2026

    @stitesExpensify
    Contributor

    Not overdue

  18. clarajones-expensify commented on Jan 27, 2026

    @clarajones-expensify
    Contributor

    Payment Summary here

  19. garrettmknight commented on Mar 16, 2026

    @garrettmknight
    Contributor

    $250 approved for @sobitneupane

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorNeeds ReproductionReproducible steps needed

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions