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
[HOLD for payment 2024-07-24] Pay someone - System message thread does not show up on LHN #44586
Version Number: 9.0-3.1 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
👋 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.
@hayata-suenaga FYI 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
Please re-state the problem that we are trying to solve in this issue.
System message thread is missing on LHN
What is the root cause of that problem?
When we pay someone, the paid system message is the send money action and the child of this action is transaction thread report.
If the report is the one transaction thread we don't show it in LHN here) but we still can access to this report . This bug also happens if we access to the transaction thread report of the combine report.
What changes do you think we should make in order to solve the problem?
I don't think it makes sense to hide the transaction thread report in LHN if it's the one transaction thread because we still can access this report via deeplink or go back from the child thread of this report. I think we can remove this check.
This issue is reproducible after #43742. Previously, the paid system message was combined into the one-transaction report so it's not possible for the user to open the paid system message thread manually, but now we show it so the users know the paid method.
What changes do you think we should make in order to solve the problem?
Because we make an exception to the combined report actions for the paid system message, we should do the same for shouldReportBeInOptionList by ignoring it if it's a paid action.
Activity
melvin-bot commentedon Jun 28, 2024
Triggered auto assignment to @hayata-suenaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jun 28, 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:
lanitochka17 commentedon Jun 28, 2024
@hayata-suenaga FYI 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
dominictb commentedon Jun 28, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
System message thread is missing on LHN
What is the root cause of that problem?
When we pay someone, the paid system message is the send money action and the child of this action is transaction thread report.
If the report is the one transaction thread we don't show it in LHN here) but we still can access to this report . This bug also happens if we access to the transaction thread report of the combine report.
What changes do you think we should make in order to solve the problem?
I don't think it makes sense to hide the transaction thread report in LHN if it's the one transaction thread because we still can access this report via deeplink or go back from the child thread of this report. I think we can remove this check.
App/src/libs/ReportUtils.ts
Lines 5434 to 5436 in 1d607ac
What alternative solutions did you explore? (Optional)
Display not found page if it doesn't show in LHN.
bernhardoj commentedon Jun 28, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
The paid system message thread doesn't show in LHN.
What is the root cause of that problem?
The paid system message thread is a one-transaction thread and we don't show a one-transaction thread in LHN.
App/src/libs/ReportUtils.ts
Lines 5433 to 5436 in 1d607ac
This issue is reproducible after #43742. Previously, the paid system message was combined into the one-transaction report so it's not possible for the user to open the paid system message thread manually, but now we show it so the users know the paid method.
What changes do you think we should make in order to solve the problem?
Because we make an exception to the combined report actions for the paid system message, we should do the same for
shouldReportBeInOptionListby ignoring it if it's a paid action.hayata-suenaga commentedon Jun 28, 2024
@bernhardoj's solution seems to address the cause. Assining @bernhardoj. @bernhardoj, is it possible to open a PR as soon as possible?
29 remaining items
JmillsExpensify commentedon Jul 30, 2024
$250 approved for @bernhardoj
eVoloshchak commentedon Aug 5, 2024
Regression Test Proposal
JmillsExpensify commentedon Aug 5, 2024
$250 approved for @eVoloshchak. Re-opening for regression test.
muttmuure commentedon Aug 7, 2024
Will handle in the morning
melvin-bot commentedon Aug 13, 2024
@muttmuure, @bernhardoj Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Aug 15, 2024
@muttmuure, @bernhardoj Still overdue 6 days?! Let's take care of this!
muttmuure commentedon Aug 19, 2024
Regression test created