Rules - Deleted field requirements rule disappears instead of showing crossed-out in offline

[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.47-0
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: #96591
Email or phone of affected tester (no customers): applausetester+ssndjois2jd1@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in with Expensifail account.
• Enable Rules.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories.
3. Open any category.
4. Click Create new rule.
5. Create Flag for review rule and Field requirements rule.
6. Go offline.
7. Go to workspace settings > Rules > Flag for review.
8. Delete flag for review rule in Step 5.
9. Go to workspace settings > Rules > Field requirements.
10. Delete field requirements rule in Step 5.
11. Open the category whose rules are deleted in Step 8 and 10.

Expected Result:

Deleted field requirements rule should be crossed out in offline mode, similar to flag for review rule.

Actual Result:

Deleted field requirements rule disappears instead of showing crossed-out in offline mode.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7222647_1785495629655.3.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7222647

Issue Owner

Current Issue Owner: @Krishna2323

[applause-bot]

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

[melvin-bot]

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

[melvin-bot]

@JS00001 @situchan you have been assigned to this deploy blocker because you reviewed the offending PR: #96591

[melvin-bot]

@Krishna2323 you have been assigned to this deploy blocker because you authored the offending PR: #96591

[melvin-bot]

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

[github-actions]

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