Skip to content

[Due for payment 2026-01-28] [$250] Report - "Tag" field is not visible on report on members' side. #75989

Closed

Description

@nlemma

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.63-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-2155/folder/13176676/41237298/1035950448
Email or phone of affected tester (no customers): ibellicotest+2119@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Have two accounts opened on two different devices or environments.
Prerequisite 2: User A has at least one workspace with "Tags" enabled and at least two tags created.

  1. Open the Expensify app.
  2. Open workspace chat.
  3. Mention User B and select "Invite to chat only" on whisper message.
  4. As User A, create a tagged manual expense.
  5. As User B, navigate to workspace chat.
  6. Note that preview of the just created expense, shows the selected tag.
  7. Open expense report.
  8. Note that "Tag" field is not visible.
  9. As User A, open expense report.
  10. Navigate to "Tag" and select a different tag.
  11. As User B, note that system message about the just changed tag is displayed, but "Tag" field is still not visible.

Expected Result:

When admin of a workspace creates a tagged expense, "Tag" field should be also visible on report on member´s side.

Actual Result:

When adming of a workspace creates a tagged expense, "Tag" field is not visible on report on member´s side. Member can see system messages about tag changes or editions, but "Tag" field doesn´t appear.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug7012747_1764050043940.Member_Tag.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021994424793346093083
  • Upwork Job ID: 1994424793346093083
  • Last Price Increase: 2025-12-05
Issue OwnerCurrent Issue Owner: @bfitzexpensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @bfitzexpensify (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. samranahm commented on Nov 25, 2025

    @samranahm
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Report - "Tag" field is not visible on report on members' side.

    What is the root cause of that problem?

    Members invited to 'chat only' cannot see tag fields because the visibility condition requires policy tag data, which may not be loaded for non-workspace members. Tags should be visible whenever they exist on a transaction.

    const shouldShowTag = (isPolicyExpenseChat || isExpenseUnreported) && (transactionTag || hasEnabledTags(policyTagLists));

    What changes do you think we should make in order to solve the problem?

    we should show tags if

    • (1) it's a policy expense chat OR unreported expense AND (2) transaction has tags OR tags are enabled

    • Also show if transaction has tags (for members who don't have full policy access)

        const shouldShowTag = ((isPolicyExpenseChat || isExpenseUnreported) && (transactionTag || hasEnabledTags(policyTagLists))) || !!transactionTag;

    const shouldShowTag = (isPolicyExpenseChat || isExpenseUnreported) && (transactionTag || hasEnabledTags(policyTagLists));

    What alternative solutions did you explore? (Optional)

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 28, 2025
  5. changed the title [-]Report - "Tag" field is not visible on report on members' side.[/-] [+][$250] Report - "Tag" field is not visible on report on members' side.[/+] on Nov 28, 2025
  6. melvin-bot commented on Nov 28, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 28, 2025
  8. melvin-bot commented on Nov 28, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan (External)

  9. moved this to Bugs and Follow Up Issues in #expensify-bugson Nov 28, 2025
  10. 44 remaining items

  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 21, 2026
  12. changed the title [-][$250] Report - "Tag" field is not visible on report on members' side.[/-] [+][Due for payment 2026-01-28] [$250] Report - "Tag" field is not visible on report on members' side.[/+] on Jan 21, 2026
  13. melvin-bot commented on Jan 21, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  14. melvin-bot commented on Jan 21, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.5-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-01-28. 🎊

    For reference, here are some details about the assignees on this issue:

    • @situchan requires payment (Needs manual offer from BZ)
  15. melvin-bot commented on Jan 21, 2026

    @melvin-bot

    @situchan @bfitzexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  16. bfitzexpensify commented on Feb 2, 2026

    @bfitzexpensify
    Contributor

    Offer sent via Upwork @situchan - please complete the BZ checklist

  17. situchan commented on Feb 2, 2026

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

      Link to comment: The root cause of original bug was in backend

    • [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: N/A

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

      Link to issue:

    Regression Test Proposal

    Precondition:

    • Have two accounts opened on two different devices or environments.
    • User A has at least one workspace with "Tags" enabled and at least two tags created.

    Test:

    1. Open workspace chat.
    2. Mention User B and select "Invite to chat only" on the whisper message.
    3. As User A, create an expense with an empty tag
    4. As User B, navigate to workspace chat
    5. Open expense report
    6. Verify the empty tag field should be hidden

    Do we agree 👍 or 👎

  18. bfitzexpensify commented on Feb 2, 2026

    @bfitzexpensify
    Contributor

    Payment complete

  19. moved this from Bugs and Follow Up Issues to Done in #expensify-bugson Feb 2, 2026
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 contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions