-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$500] LHN - Expense details report title does not show the amount in LHN after relogin #32382
Comments
👋 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:
|
Triggered auto assignment to @joelbettner ( |
I don't think this is blocker. Staging is even better than production which shows nothing in LHN title Before opening reports:Staging:Production:After reverting #31302:After opening reports: |
@situchan I agree that this should not be a blocker, since it is at least an improvement over production. |
Job added to Upwork: https://www.upwork.com/jobs/~012c05b0ef5839e23d |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra ( |
@situchan do you have any ideas for a solution? |
The solution is limited. I don't think of any better solution in frontend just to show "Request" unless backend supports something for that. |
We decided to simply display |
Agree. We can close this @joelbettner |
ProposalPlease re-state the problem that we are trying to solve in this issue.The title for expense details report in LHN does not show the amount at all after relogin. It only shows the amount after opening the report What is the root cause of that problem?When the report first loads, it doesn't have transaction data, so only What changes do you think we should make in order to solve the problem?We should rely on the fields of the money request report to show the title in LHN if transaction data is not available. We already do the same for the Expense report, that's why it still shows the amount correctly even after logged in again. We can use fields like I think this is much better than showing only What alternative solutions did you explore? (Optional)NA |
@dukenv0307 if something should be fixed here, #30687 should have already covered this. So it should be fixed as follow-up of #30687 by same contributors. Otherwise just close. |
@situchan I think this is more like a feature request since back-end is not supporting this. So we can't expect it to be covered by an earlier bug fix. If we want to improve the UX here, we can do it in this issue. Let's minimize discussions and see what @joelbettner thinks. |
@joelbettner Bump here |
@situchan @dukenv0307 @shubham1206agra Can you please tell me what API call is used to gather the information that we use to display the info in the LHN for these money requests, and what information we'd need to make them look consistent with the information that is displayed after the report has been opened? I'll research what it would take to return that information. |
@joelbettner When we open the App, all reports that are displayed in LHN are returned by Lines 1901 to 1902 in ab4449c
So for transaction thread report, we should add some data like |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
ProposalPlease re-state the problem that we are trying to solve in this issue.In LHN, the title or name of chat thread of IOU request doesn't display full text after user logout then login What is the root cause of that problem?When user logut then login, the back end doesn't return all transactions data and when LHN is rendered the getTransactionReportName will fall in this section: Lines 1900 to 1902 in 86a2521
What changes do you think we should make in order to solve the problem?We could use reportAction message data instead of displaying What alternative solutions did you explore? (Optional) |
@joelbettner, @shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@joelbettner, @shubham1206agra Eep! 4 days overdue now. Issues have feelings too... |
@joelbettner bump |
@puneetlath Yes that’s correct , that's the expected behaviour : the |
Sorry...I'm just tied down with some other work before I can get to making those changes in |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@joelbettner, @shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
1 similar comment
@joelbettner, @shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I'm going to close this for now and this is the currently the intended bahavior. Perhaps the issue can be re-visited in the future if we change what our intended behavior is like. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.7-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #31302
Action Performed:
Expected Result:
The title for expense details report in LHN shows the correct amount
Actual Result:
The title for expense details report in LHN does not show the amount at all after relogin. It only shows the amount after opening the report
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6297756_1701457553231.Screen_Recording_20231202_003805_Chrome.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: