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
[Due for payment 2025-06-05] [Better Expense Report View] [$250] Only the header & bottom padding of preview are highlighted after submitting expense #62560
Version Number: 9.1.49-4 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):sjjsksksksjsjsjs@gmail.com Issue reported by: Applause Internal Team Device used: iPhone 15 Pro Max / iOS 18.4 App Component: Search
Action Performed:
Launch Expensify app.
Go to workspace chat.
Submit an expense.
Go to Reports.
Tap bookmark icon.
Tap Expense Reports.
Open FAB > Create expense > Manual.
Submit another expense to the same workspace chat.
Expected Result:
After submitting expense, the entire expense report row will be highlighted briefly.
Actual Result:
After submitting expense, only the header and bottom padding of the expense report row are highlighted briefly.
👋 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:
Identify the pull request that introduced this issue and revert it.
@adelekennedy FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
changed the title [-]Reports - Only the header & bottom padding of preview are highlighted after submitting expense[/-][+][$250] Reports - Only the header & bottom padding of preview are highlighted after submitting expense[/+]on May 22, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.53-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann@adelekennedy@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]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] 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:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Go to workspace chat.
Submit an expense.
Go to Reports.
Tap bookmark icon.
Tap Expense Reports.
Open FAB > Create expense > Manual.
Submit another expense to the same workspace chat.
After submitting expense, the entire expense report row will be highlighted briefly.
Activity
melvin-bot commentedon May 22, 2025
Triggered auto assignment to @adelekennedy (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon May 22, 2025
Triggered auto assignment to @inimaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 22, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 22, 2025
👋 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:
nlemma commentedon May 22, 2025
@adelekennedy FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
[-]Reports - Only the header & bottom padding of preview are highlighted after submitting expense[/-][+][$250] Reports - Only the header & bottom padding of preview are highlighted after submitting expense[/+]34 remaining items
melvin-bot commentedon May 29, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 29, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.53-7 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-06-05. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 29, 2025
@DylanDylann @adelekennedy @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]
adelekennedy commentedon Jun 6, 2025
Payment Summary
Contributor: @nkdengineer paid $250 via Upwork
Contributor+: @DylanDylann due $250 via NewDot
adelekennedy commentedon Jun 6, 2025
@DylanDylann for checklist
DylanDylann commentedon Jun 6, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] 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:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Jun 9, 2025
@adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!
JmillsExpensify commentedon Aug 12, 2025
$250 approved for @DylanDylann
quinthar commentedon Aug 13, 2025
$250 approved for @DylanDylann