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
[Due for payment 2026-03-04] Clicking "Workspace rule" text link in system message doesn't lead to help page #82978
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:
Prepare two accounts (Admin and Member)
(Admin) create a workspace and invite the member to the workspace
(Admin) enable workspace rules in more feature
(Admin) add one or more merchant rules
Steps:
(Admin) create an expense with merchant that already set in merchant rules
(Admin) open the expense details
(Admin) Click "Workspace rule" text link on the system message
(Member) create an expense with merchant that already set in merchant rules
(Member) open the expense details
(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.
👋 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:
Identify the pull request that introduced this issue and revert it.
[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.
Activity
melvin-bot commentedon Feb 19, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #82438
melvin-bot commentedon Feb 19, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Feb 19, 2026
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.github-actions commentedon Feb 19, 2026
👋 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:
luacmartins commentedon Feb 19, 2026
We reverted the PR. This is NAB.
29 remaining items
melvin-bot commentedon Mar 6, 2026
@luacmartins, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Mar 9, 2026
Triggered auto assignment to @NicMendonca (
Awaiting Payment)NicMendonca commentedon Mar 10, 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.
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 👎
NicMendonca commentedon Mar 10, 2026
@situchan does this need a BZ checklist?
situchan commentedon Mar 10, 2026
No need. We created comprehensive regression test in separate issue.
NicMendonca commentedon Mar 10, 2026
Just sent you the offer on Upwork
NicMendonca commentedon Mar 10, 2026
Payment Summary