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-04-25] Split - Individual split amount input is cut off #60240
Version Number: 9.1.28-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A 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):applausetester+sdsoidsj@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Money Requests
👋 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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.29-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@MariaHCD / @marcaaron@sonialiap@MariaHCD / @marcaaron 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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
⚠️ Hold for payment automation failed -> this should be on [HOLD for payment 2025-04-23] according to production deploy from #60259 (comment) (10 hours ago).
Only I require payment here as C+ reviewer for the PR (was assigned from Slack to help review deploy blocker asap).
Activity
melvin-bot commentedon Apr 15, 2025
Triggered auto assignment to @sonialiap (
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 Apr 15, 2025
Triggered auto assignment to @MariaHCD (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 15, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Apr 15, 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:
MariaHCD commentedon Apr 15, 2025
Looks to happen for any three letter currency code:
MariaHCD commentedon Apr 15, 2025
I think this might be from #59792
cc: @Krishna2323 @DylanDylann could you check?
18 remaining items
melvin-bot commentedon Apr 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.29-10 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-04-25. 🎊
melvin-bot commentedon Apr 18, 2025
@MariaHCD / @marcaaron @sonialiap @MariaHCD / @marcaaron 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]
ikevin127 commentedon Apr 23, 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: https://github.com/Expensify/App/pull/59792/files#r2055085729.
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:https://github.com/Expensify/Expensify/issues/494145
Regression Test Proposal
AED - Dhsfrom Settings > Preferences.Do we agree 👍 or 👎.
cc @sonialiap Circling back to my previous comment:
sonialiap commentedon Apr 25, 2025
Payment summary
ikevin127 commentedon Apr 25, 2025
@sonialiap Offer accepted, thank you!
marcaaron commentedon Apr 28, 2025
Nice I think this can be closed?
ikevin127 commentedon Apr 28, 2025
@marcaaron Payment was not completed yet, I accepted the offer but did not receive the payment yet.
cc @sonialiap
sonialiap commentedon Apr 29, 2025
Payment completed 🚀