Skip to content

[Due for payment 2026-03-04] Clicking "Workspace rule" text link in system message doesn't lead to help page #82978

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: v9.3.22-2
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #82438
Email or phone of affected tester (no customers): applausetester+piyomn@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 13 / iOS 18.7.1, Samsung Galaxy A52 / Android 14, Windows 11 / Chrome
App Component: Workspace Settings

Action Performed:

Preconditions:

  1. Prepare two accounts (Admin and Member)
  2. (Admin) create a workspace and invite the member to the workspace
  3. (Admin) enable workspace rules in more feature
  4. (Admin) add one or more merchant rules

Steps:

  1. (Admin) create an expense with merchant that already set in merchant rules
  2. (Admin) open the expense details
  3. (Admin) Click "Workspace rule" text link on the system message
  4. (Member) create an expense with merchant that already set in merchant rules
  5. (Member) open the expense details
  6. (Member) Click "Workspace rule" text link on the system message

Expected Result:

in step 3 and step 6, both admin and member, when clicking "workspace rule" should leads to help page.

Actual Result:

  • in step 3, when an admin creates an expense, clicking the "workspace rule" text link leads to the workspace rules settings.
  • in step 6, when a member creates an expense, clicking the "workspace rule" text link goes to a “Not Here” page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7082668_1771522096810.text_link.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Feb 19, 2026

    @melvin-bot

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

  4. melvin-bot commented on Feb 19, 2026

    @melvin-bot

    Triggered auto assignment to @sonialiap (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.

  5. github-actions commented on Feb 19, 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.
  6. luacmartins commented on Feb 19, 2026

    @luacmartins
    Contributor

    We reverted the PR. This is NAB.

  7. 29 remaining items

  8. melvin-bot commented on Mar 6, 2026

    @melvin-bot

    @luacmartins, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Mar 9, 2026
  10. melvin-bot commented on Mar 9, 2026

    @melvin-bot

    Triggered auto assignment to @NicMendonca (Awaiting Payment)

  11. NicMendonca commented on Mar 10, 2026

    @NicMendonca
    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:

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

    Regression Test Proposal Template
    • [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:

    Test:

    Do we agree 👍 or 👎

  12. NicMendonca commented on Mar 10, 2026

    @NicMendonca
    Contributor

    @situchan does this need a BZ checklist?

  13. situchan commented on Mar 10, 2026

    @situchan
    Contributor

    No need. We created comprehensive regression test in separate issue.

  14. NicMendonca commented on Mar 10, 2026

    @NicMendonca
    Contributor

    Just sent you the offer on Upwork

  15. NicMendonca commented on Mar 10, 2026

    @NicMendonca
    Contributor

    Payment Summary

    • Contributor: @situchan paid $250 via Upwork (✅ )
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.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions