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-10-11] [HOLD for payment 2024-10-10] [$250] [Search v2.2] Reload the page and highlight the newly added expense when adding a new expense from the search page #48716
When the new expense is added to the search page, trigger a reload of the page so it can appear in the table.
I think we might need to just trigger a reload of the page given the existing filters may or may not show the new transation.
Highlight the newly added expense row in the table when it appears
For this, we were thinking it could borrow from the workspace settings when you enable a new feature in More features, and the row gets highlighted in the LHN briefly.
Once we've done that, we'll add this regression test for Applause:
Switch to the search page tab
Click the global create button > submit expense > submit an expense
Verify you remain on the search page
Verify the search page reloads and the expense appears in the table
Verify the newly added expense row is briefly highlighted to draw attention to it
We do use a highlight color on chats but I'm personally not a huge fan of this due to how muddy it looks. If we apply it here I don't think it looks great:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@ikevin127] The PR that introduced the bug has been identified. Link to the PR:
[@ikevin127] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@ikevin127] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@ikevin127] Determine if we should create a regression test for this bug.
[@ikevin127] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
📣 @ishpaul777 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
changed the title [-][HOLD for payment 2024-10-10] [$250] [Search v2.2] Reload the page and highlight the newly added expense when adding a new expense from the search page[/-][+][HOLD for payment 2024-10-11] [HOLD for payment 2024-10-10] [$250] [Search v2.2] Reload the page and highlight the newly added expense when adding a new expense from the search page[/+]on Oct 4, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.44-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@ikevin127 / @ishpaul777] The PR that introduced the bug has been identified. Link to the PR:
[@ikevin127 / @ishpaul777] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@ikevin127 / @ishpaul777] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@ikevin127 / @ishpaul777] Determine if we should create a regression test for this bug.
[@ikevin127 / @ishpaul777] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
[@ikevin127] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A.
[@ikevin127] Determine if we should create a regression test for this bug.
[@ikevin127] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
Regression Test Proposal
Switch to the Search page tab.
Click the global create button (FAB) > Submit expense > Submit an expense.
Verify you remain on the Search page.
Verify that the newly added expense appears in the table and the row is briefly highlighted to draw attention to it.
Do we agree 👍 or 👎.
Reacted by Jon Dubielzyk, Ishpaul Singh and Tom Rhys Jones
Activity
melvin-bot commentedon Sep 6, 2024
Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.
melvin-bot commentedon Sep 6, 2024
Triggered auto assignment to @dubielzyk-expensify (
Design), see these Stack Overflow questions for more details.trjExpensify commentedon Sep 6, 2024
Can we get a mock of the row highlighted to include here, please? Thanks!
ikevin127 commentedon Sep 7, 2024
♻️ Will look into this tomorrow, the plan being to come up with a proposal and some videos for the design team to review 👍
dubielzyk-expensify commentedon Sep 9, 2024
Animation 1: Just color fade
CleanShot.2024-09-09.at.20.06.20.mp4
Animation 2: Slide and color fade
CleanShot.2024-09-09.at.20.06.36.mp4
Animation 3: Color fade and stay
CleanShot.2024-09-09.at.20.10.45.mp4
No animation: Use
highlight statecolorWe do use a highlight color on chats but I'm personally not a huge fan of this due to how muddy it looks. If we apply it here I don't think it looks great:

cc @Expensify/design team for thoughts
52 remaining items
melvin-bot commentedon Oct 3, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
ishpaul777 commentedon Oct 4, 2024
👋 Please assign me here i reviewed #49192
melvin-bot commentedon Oct 4, 2024
📣 @ikevin127 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
melvin-bot commentedon Oct 4, 2024
📣 @ishpaul777 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖
[-][HOLD for payment 2024-10-10] [$250] [Search v2.2] Reload the page and highlight the newly added expense when adding a new expense from the search page[/-][+][HOLD for payment 2024-10-11] [HOLD for payment 2024-10-10] [$250] [Search v2.2] Reload the page and highlight the newly added expense when adding a new expense from the search page[/+]melvin-bot commentedon Oct 4, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.44-12 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 2024-10-11. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 4, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
ikevin127 commentedon Oct 4, 2024
Regression Test Proposal
Do we agree 👍 or 👎.
trjExpensify commentedon Oct 11, 2024
Regression test created. Payment summary as follows:
Paid, closing!