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-09-19] Merge flow – Misaligned radio button with long category name #68243
Version Number: V9.1.92-1 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory Email or phone of affected tester (no customers): Slottwo1 7423@gmail.com Issue reported by: Applause Internal Team Device used: Redminote 10s android 13 phone App Component: Money Requests
Action Performed:
Launch app in both mweb and Android
Open workpace chat
Tap category
Add a long category - Advertisingradhe-krishna-dfgggggghhhhhhh-hhhhhhhhh-hhhhhhhhhghbbnnbbbb-radhe-radherradhe-krishncvbbnhhjjjjjjjh Hbb.com
Create 2 expenses with merchant and category. For any one expense select the long category
Open the expense in which long category is not selected
Tap more - merge - select the expense with long category
Note in mweb and Android
Expected Result:
In merge flow, when long category name is entered radio button placement must not be misaligned.
Actual Result:
In merge flow, when long category name is entered radio button placement is misaligned in android and not in mweb.
👋 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 [-]Merge flow – Misaligned radio button with long category name[/-][+][Due for payment 2025-09-19] Merge flow – Misaligned radio button with long category name[/+]on Sep 12, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@youssef-lr@garrettmknight 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]
Activity
melvin-bot commentedon Aug 9, 2025
Triggered auto assignment to @garrettmknight (
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 Aug 9, 2025
Triggered auto assignment to @marcaaron (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 9, 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 Aug 9, 2025
💬 A slack conversation has been started in #expensify-open-source
Krishna2323 commentedon Aug 9, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
Merge flow – Misaligned radio button with long category name
What is the root cause of that problem?
App/src/pages/TransactionMerge/MergeFieldReview.tsx
Line 39 in dd11c95
What changes do you think we should make in order to solve the problem?
styles.flex1to the text styles.What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
N/A
What alternative solutions did you explore? (Optional)
Result
hoangzinh commentedon Aug 11, 2025
I fixed in this commit fc9e2e3
13 remaining items
garrettmknight commentedon Aug 29, 2025
Can't test on current adhoc build (no android), will need to test on another adhoc build or on staging..
garrettmknight commentedon Sep 3, 2025
Same as above, I think we can test this when we deploy. It's super small.
melvin-bot commentedon Sep 11, 2025
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.
[-]Merge flow – Misaligned radio button with long category name[/-][+][Due for payment 2025-09-19] Merge flow – Misaligned radio button with long category name[/+]melvin-bot commentedon Sep 12, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 12, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.12-4 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-09-19. 🎊
melvin-bot commentedon Sep 12, 2025
@youssef-lr @garrettmknight 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]