Expense - Transaction thread with violation does not appear in LHN

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Found when validating PR : #35449

Version Number: v1.4.44-7
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team

Action Performed:

Precondition:

• User is an employee of Collect workspace.
• The Collect workspace has Category and Tag set to "Required".

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create a manual request without category and tag.

Expected Result:

The transaction thread with violation will appear in LHN.

Actual Result:

The transaction thread with violation does not appear in LHN unless it is visited.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6395021_1709091888120.bandicam_2024-02-28_02-49-56-207.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[izarutskaya]

@MitchExpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[izarutskaya]

We think that this bug might be related to #wave6-collect-submitters
CC @greg-schroeder

[MitchExpensify]

This does look like wave 6 to me too, what do you think @greg-schroeder ?

[MitchExpensify]

Not sure how the quarterly release impacts this issue's priority, I still think confirming if its a wave 6 related issue is a good first step so bumpin ya for an opinion there @greg-schroeder

[melvin-bot]

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