Skip to content

[Due for payment 2026-09-17] Expense- On confirm page, Tag row does not highlight when it appears after changing workspace #100771

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.75-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #100191
Email or phone of affected tester (no customers): jsdoijnodsdisojo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Create two workspaces - A and B.
  • Workspace A is the default workspace with at least one tag.
  1. Go to staging.new.expensify.com
  2. Open FAB > Create expense > Manual.
  3. Click To field.
  4. Select workspace B.
  5. Click To field.
  6. Select workspace A.

Expected Result:

Tag row will highlight as it animates in.

Actual Result:

Tag row does not highlight as it animates in.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7255480_1788988324028.9.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7255480

Issue OwnerCurrent Issue Owner: @Pujan92

Activity

  1. applause-bot commented on Sep 9, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/accd70bc658537741370b9620ae776d9b760e7418aa2f30d2ede25335f554206

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 9, 2026
  3. melvin-bot commented on Sep 9, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #100191

  4. github-actions commented on Sep 9, 2026

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. melvin-bot commented on Sep 9, 2026

    @melvin-bot

    @roryabraham @Pujan92 @JakubKorytko you have been assigned to this deploy blocker because you reviewed the offending PR: #100191

  6. melvin-bot commented on Sep 9, 2026

    @melvin-bot

    @war-in you have been assigned to this deploy blocker because you authored the offending PR: #100191

  7. melvin-bot commented on Sep 9, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  8. 1 remaining item

  9. blimpich commented on Sep 9, 2026

    @blimpich
    Contributor

    consolidating conversation around this deploy blocker and it's related deploy blockers here: https://expensify.slack.com/archives/C01GTK53T8Q/p1788996794073959

  10. melvin-bot commented on Sep 10, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  11. IuliiaHerets commented on Sep 10, 2026

    @IuliiaHerets

    This issue is not repro on Windows 10/Chrome Build v9.4.75-1

    Recording.1576.mp4
  12. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 10, 2026
  13. changed the title [-]Expense- On confirm page, Tag row does not highlight when it appears after changing workspace[/-] [+][Due for payment 2026-09-17] Expense- On confirm page, Tag row does not highlight when it appears after changing workspace[/+] on Sep 10, 2026
  14. melvin-bot commented on Sep 10, 2026

    @melvin-bot

    @Pujan92 / @abzokhattab / @TaduJR

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.75-3 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-09-17. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]. If no checklist is needed for this issue, you can click: [no checklist button]

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions