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 2026-10-16] [$175] [CFI] Edit bank account names in New Expensify #101251
Coming from this Slack thread, let's let users rename their bank accounts in New Expensify so they can distinguish accounts with similar ending digits.
Details
Classic supports an editable Account Name field on eligible bank accounts. It updates the existing addressName field.
New Expensify already receives and displays this same field as the bank-account title, but does not provide a way to edit it. IE if you edit a name today in classic, the custom name appears in New Expensify
Add an editable Edit nickname field to eligible bank accounts in Wallet, for both personal and business bank accounts.
Persist changes through the existing bank-account update path, updating addressName. This is not a new alias data model or backend feature.
Keep the same editability rules as Classic. Classic only allows editing the field when the bank account is in the OPEN state.
Existing Classic account names should continue to display in New Expensify, and edits made in either product should be reflected in the other after the bank-account data refreshes.
UX: Tapping edit nickname button opens RHP with edit field. Default name is listed there, user can edit away from that. Field can't be empty.
NewDot nickname flow
Issue OwnerCurrent Issue Owner: @mallenexpensifyUpwork Automation - Do Not Edit
We could just say name, but I think nickname helps communicate that this is just a name that changes in Expensify and not the name as a whole. Might also need copy help from someone on the RHP part.
(Sidenote: Once we have Business Wallet/Treasury, we're likely gonna have a Bank Details RHP for all bank accounts. In that world, I expect nickname to just be a push input. So I think this simple direction can work for now)
Nice, yep, looks good to me. The only thing I would expect is the original name we give to the account to be the default for this field, rather than having it be blank. And then the user can change it from that.
Deploy Blocker #103538 was identified to be related to the PR #102366 that attempted to fix this issue.
@shubham1206agra this issue and/or PR mention a deploy blocker or a regression. Before the payment date, post one of the three options in step 20 of the C+ doc: it was a regression, it was not, or you did not review the offending PR. If you don't post, the default is to reduce payment.
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA
Link to the comment on the Issue: NA
[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: NA
[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.
Regression Test Proposal
Precondition:
Account has an open personal bank account and an open business bank account in Wallet.
Test:
Go to Account > Wallet.
Click the three-dot menu on the personal bank account.
Verify that an "Edit nickname" option appears.
Click "Edit nickname".
Verify that the "Nickname" field is prefilled with the name shown on the Wallet row.
Clear the field and click "Save".
Verify that a "This field is required" error appears and the page stays open.
Enter a new nickname and click "Save".
Verify that the page closes and the Wallet row shows the new nickname.
Refresh the page.
Verify that the Wallet row still shows the new nickname.
Repeat steps 2 to 11 with the business bank account.
Activity
melvin-bot commentedon Sep 15, 2026
Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (
NewFeature)joekaufmanexpensify commentedon Sep 15, 2026
@dubielzyk-expensify Let me know your thoughts on UX here or if you have any questions on the feature!
dubielzyk-expensify commentedon Sep 16, 2026
On it! Should be a quick one 👍
joekaufmanexpensify commentedon Sep 16, 2026
thanks!
dubielzyk-expensify commentedon Sep 17, 2026
What about something like..... THIS!?
Set nickname
Edit nickname or remove once saved
We could just say name, but I think nickname helps communicate that this is just a name that changes in Expensify and not the name as a whole. Might also need copy help from someone on the RHP part.
cc @Expensify/design for feedback too
dubielzyk-expensify commentedon Sep 17, 2026
(Sidenote: Once we have Business Wallet/Treasury, we're likely gonna have a Bank Details RHP for all bank accounts. In that world, I expect nickname to just be a push input. So I think this simple direction can work for now)
shawnborton commentedon Sep 17, 2026
That looks great to me, and yeah I think the simple direction is a good v1 until we have RHP views for these accounts.
joekaufmanexpensify commentedon Sep 17, 2026
Nice, yep, looks good to me. The only thing I would expect is the original name we give to the account to be the default for this field, rather than having it be blank. And then the user can change it from that.
64 remaining items
melvin-bot commentedon Oct 15, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 15, 2026
Payment Summary
Resolving PRs:
Let users edit bank account nicknames in Wallet #102366
Reviewer: @shubham1206agra owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 17, 2026
@shubham1206agra this issue and/or PR mention a deploy blocker or a regression. Before the payment date, post one of the three options in step 20 of the C+ doc: it was a regression, it was not, or you did not review the offending PR. If you don't post, the default is to reduce payment.
shubham1206agra commentedon Oct 20, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: NA
Link to the comment on the Issue: NA
[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: NA
[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.
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
shubham1206agra commentedon Oct 20, 2026
@mallenexpensify About DB linked here
#103538 - Dev environment only issue due to BE restrictions, works well in production.
mallenexpensify commentedon Oct 20, 2026
Payment Summary
Contributor+: @shubham1206agra due $175 via NewDot