-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Due for payment 2025-05-14] [Better Expense Report View] Report view follow-ups #59459
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
Comments
Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new. |
thanks @trjExpensify!
Can be done inside the selection PR because: 1) its a super small change 2) this PR will have to touch row styling anyway because of active/hover/selected styling and these styles are connected
[This is info mainly for developers] I believe this refreshing bug will have the same RCA as requiring a refresh after deleting an expense (CC @jnowakow so you are aware) |
There is one more bug we have noticed (but not created an issue yet). Right now the expectation is that on Reports (old Search) if you choose This expectation is clear, but I wanted to discuss the fix of the bug with @mountiny and @luacmartins (especially I hope Carlos remembers parts of how search was originally designed 😅). The root cause is that on Reports results we differentiate between a rows that represent a transaction: and a row that represents a report: ![]() These two have different What I find surprising is that results from backend even when we do Thoughts? |
Well, even the single expense report is just a report. Could you add a check that will compare the size of the transactions list and if its just one transaction open it in RHP? @Kicu, also do you have an example of the confusing response? Are you suggesting that we return both the reports style data AND then we duplicate the transactions data in the transaction object response if its single expense report? |
Sure, but that wouldn't be a full final solution, because the expectation is that if you're on "Expenses" part of I can of course pass down some kind of context to know "from where" you are clicking but originally I thought I can base this on the type of result row.
Actually I did a deeper dig into the FE code and I think its the frontends fault for treating these items sometimes as a report and sometimes as a transaction. So my bad. I think there is no need to change how backend returns stuff. |
Ok great, sounds like this is covered now, I do code in the backend |
umm @trjExpensify this is the first time I'm seeing these new headers on results 😅 Is the expectation that we do it as part of the new Report View or something we plan to do later? |
The empty state header is part of Report Creation UI, so we'll be updating them there to be consistent with that. Issue is here. |
oh ok thanks 👍 |
It seems like this is sorted out. Let me know if I can help with anything |
Yeah, seems like pretty much anything I update in the expense detail screen doesn't update in the table automatically either. |
@trjExpensify issues from |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Fresh follow up: the PR to navigate to expense report table view in Inbox (#60119) grew quite big so we plan to merge it soon. |
This is close to being closed out. Hover style on the selected transaction row is not correct & Incorrect position and padding on the row on the reports page - @Kicu are we still awaiting a PR for these, or did I miss it? |
this is the PR that will fix it: #61159 although its not ready yet. Sorry I bundled this up with some other small UI tweaks to save time on creating PRs and reviewing so it took a while ;) |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.41-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-05-14. 🎊 For reference, here are some details about the assignees on this issue:
|
@allgandalf / @DylanDylann @trjExpensify @allgandalf / @DylanDylann The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Going to close this now. |
Uh oh!
There was an error while loading. Please reload this page.
This is a list of follow up tasks related to the expense report view we're aware of to handle after this PR has merged: #58903
Assigned a bunch of us to keep track of it. Let's link out to where the items are being taken care of as we chomp through them. Thanks!
Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: