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-08-11] Expense - A to B and B to A indicators are displayed on three lines #67319
Version Number: 9.1.87-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:#66260 Email or phone of affected tester (no customers):saosijnaosasjo@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
[User A] Submit an expense to User B.
[User B] Submit an expense to User A.
Expected Result:
A to B and B to A indicators will be displayed on the same line.
Actual Result:
A to B and B to A indicators are displayed on three lines.
👋 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.
changed the title [-]Expense - A to B and B to A indicators are displayed on three lines[/-][+][Due for payment 2025-08-11] Expense - A to B and B to A indicators are displayed on three lines[/+]on Aug 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.88-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hungvu193@OfstadC 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]
[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: N/A
[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.
Activity
melvin-bot commentedon Jul 29, 2025
Triggered auto assignment to @OfstadC (
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.github-actions commentedon Jul 29, 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:
melvin-bot commentedon Jul 29, 2025
Triggered auto assignment to @AndrewGable (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 29, 2025
💬 A slack conversation has been started in #expensify-open-source
AndrewGable commentedon Jul 29, 2025
Pinged in Slack
17 remaining items
[-]Expense - A to B and B to A indicators are displayed on three lines[/-][+][Due for payment 2025-08-11] Expense - A to B and B to A indicators are displayed on three lines[/+]melvin-bot commentedon Aug 4, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.88-3 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-08-11. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 4, 2025
@hungvu193 @OfstadC 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]
OfstadC commentedon Aug 8, 2025
@hungvu193 please complete BZ checklist prior to payment date - Thank you!
hungvu193 commentedon Aug 10, 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: Came from Refactor TransactionItemRow for better performance #66169, we already discussed it via slack
[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: N/A
[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.
Minor UI issue. No regression test needed.
OfstadC commentedon Aug 11, 2025
Payment Summary
Thank you!
garrettmknight commentedon Aug 12, 2025
$250 approved for @hungvu193
JmillsExpensify commentedon Aug 12, 2025
$250 approved for @hungvu193