Repository navigation
Expense - Transaction thread with violation does not appear in LHN #37405
Description
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".
- Go to staging.new.expensify.com
- Go to workspace chat.
- 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
Activity
melvin-bot commentedon Feb 28, 2024
Triggered auto assignment to @MitchExpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.izarutskaya commentedon Feb 28, 2024
@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 commentedon Feb 28, 2024
We think that this bug might be related to #wave6-collect-submitters
CC @greg-schroeder
MitchExpensify commentedon Mar 2, 2024
This does look like wave 6 to me too, what do you think @greg-schroeder ?
MitchExpensify commentedon Mar 5, 2024
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 commentedon Mar 8, 2024
@MitchExpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
MitchExpensify commentedon Mar 10, 2024
Wave collect worthy Señor Wave Collect, @trjExpensify ?
10 remaining items
github-actions commentedon Mar 13, 2024
👋 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:
melvin-bot commentedon Mar 13, 2024
Triggered auto assignment to @danieldoglas (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.izarutskaya commentedon Mar 13, 2024
@danieldoglas 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. Thanks
danieldoglas commentedon Mar 13, 2024
@cead22 I remember you said you found new issues with violations last Friday. Is this related?
luacmartins commentedon Mar 13, 2024
I don't think this is a blocker since Violations is still in a beta. Additionally, I think this might be because we reverted this PR due to performance issues since that PR added report errors to the LHN.
melvin-bot commentedon Mar 13, 2024
@danieldoglas @MitchExpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
cead22 commentedon Mar 14, 2024
I couldn't repro on v1.4.52-1 staging desktop web
1wBjJrPYLE.mp4