-
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
[$250] Trip summary not displayed for thread replies #56061
Comments
Triggered auto assignment to @slafortune ( |
I'm Błażej Kustra from SWM, and I'm commenting for assignment! |
Hi, I'll be helping out @blazejkustra here. |
Job added to Upwork: https://www.upwork.com/jobs/~021885343111802950570 |
Current assignee @shubham1206agra is eligible for the External assigner, not assigning anyone new. |
Assigned to myself so that there is an Expensify CME for this who is focused on travel. Removed |
Waiting for @sumo-slonik to raise a PR. |
@shubham1206agra Could you help me reproduce the bug? |
@sumo-slonik Go inside a comment thread from here. |
@shubham1206agra could you include a video of you entering the trip room and adding a comment in addition to the screenshot? |
@sumo-slonik Here you go Screen.Recording.2025-02-05.at.8.04.13.PM.mov |
thanks :D |
I managed to reproduce, without recording I did not understand the flow |
Hi @shubham1206agra @blimpich, could you confirm if the thread is working as it should in the attached video? Screen.Recording.2025-02-07.at.12.29.25.mov |
@sumo-slonik Chat header looks wrong. Also, I don't think we need trip preview in the thread. But I will let @Expensify/design decide on this. |
Hmm I am not following, do you mind rephrasing? Maybe it would be helpful to show the parent view of each step down into the thread history as well? |
@slafortune, @blimpich, @blazejkustra, @shubham1206agra, @sumo-slonik Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I'll take over as @sumo-slonik is OOO this week. I'm going leave an update later today, so stay tuned 😄 |
Yeah this would be helpful for me too. I'm having trouble following the different cases here so it's hard for me to know what the expected behavior should be. |
The issue we are trying to fix is that currently nested threads aren't displayed properly for trip rooms:
before.movMy suggested approach is to display both: trip summary and the parent message of a thread, like in this video below: fix.movLet me know if it looks good to you both @dannymcclain & @shawnborton 👀 |
Ahhh I see! So in that case, I think your second thread would just have |
Makes sense! PR is ready for review @shubham1206agra 😄 www.mov |
Good question @dannymcclain, this looks weird. I briefly looked through the code and we use the report name from the backend. Could you have a look @rlinoz / @stitesExpensify? if (isTripRoom(report)) {
return report?.reportName ?? '';
} |
This doesn't mean we have to block the above PR, as this seems unrelated. cc @shubham1206agra |
Every thread has the report name set to |
Maybe just update it to
|
I think this should work, @blazejkustra if you try this do you see any issues? |
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.0.92-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @shubham1206agra
Slack conversation (hyperlinked to channel name): travel
Action Performed:
Expected Result:
It should look like a normal thread
Actual Result:
Empty trip summary appears
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @blazejkustraThe text was updated successfully, but these errors were encountered: