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
Version Number: 9.1.13-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):[email protected] Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Submit two expenses to the workspace chat.
Go to transaction thread of any expense.
Click on the report header > Hold.
Enter reason and save it.
Dismiss RHP and education modal if needed.
Delete the hold reason in the transaction thread.
Note that the system message in transaction thread is "held this expense", but LHN preview shows "held this expense with the comment:".
Click on the header subtitle and go back to transaction thread.
Now LHN preview shows "held this money request, saying x".
Expected Result:
In Step 9 and 11, LHN preview for hold expense system message should be the same as transaction thread.
Actual Result:
In Step 9, the system message in transaction thread is "held this expense", but LHN preview shows "held this expense with the comment:".
In Step 11, after refreshing the page, LHN preview shows "held this money request, saying x".
Please re-state the problem that we are trying to solve in this issue.
Held expense - LHN preview shows inconsistent system message when expense is held
What is the root cause of that problem?
We use optionItem.alternateText to display LHN preview message. And it is calculated by getOptionData function. In getOptionData, we are not handling HOLD action type as we are doing for PureReportActionItem. And hold action is handled in the else condition by default below
What changes do you think we should make in order to solve the problem?
We should handle HOLD action in the same way we are handling them in PureReportActionItem. We should do the same for UNHOLD action if the same problem happens for unhold action too.
else if (lastAction?.actionName === CONST.REPORT.ACTIONS.TYPE.HOLD) {
result.alternateText = translateLocal('iou.heldExpense');
}
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
Add test that asserts getOptionData returns the expected value when a report's last action is hold here.
What alternative solutions did you explore? (Optional)
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.1.13-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests
Action Performed:
Expected Result:
In Step 9 and 11, LHN preview for hold expense system message should be the same as transaction thread.
Actual Result:
In Step 9, the system message in transaction thread is "held this expense", but LHN preview shows "held this expense with the comment:".
In Step 11, after refreshing the page, LHN preview shows "held this money request, saying x".
Workaround:
Unknown
Platforms:
Screenshots/Videos
bug.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: