github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 15:14:02 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #316] Duplicate Account names should not be possible. #14266

New Issue
Closed
opened 2026-04-14 17:01:39 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-14 17:01:39 -05:00
Owner
Copy Link

Originally created by @bpaulien on GitHub (Dec 5, 2021).
Original GitHub issue: https://github.com/actualbudget/actual/issues/316

Originally created by @bpaulien on GitHub (Dec 5, 2021). Original GitHub issue: https://github.com/actualbudget/actual/issues/316
GiteaMirror added the user interfacegood first issuebug labels 2026-04-14 17:01:40 -05:00
GiteaMirror commented 2026-04-14 17:01:41 -05:00
Author
Owner
Copy Link

@DistroByte commented on GitHub (Oct 18, 2022):

Can confirm you can have duplicate account names screenshot
here

<!-- gh-comment-id:1282755395 --> @DistroByte commented on GitHub (Oct 18, 2022): Can confirm you can have duplicate account names screenshot ![here](https://i.dbyte.xyz/firefox_uJVGEksxl.png)
GiteaMirror commented 2026-04-14 17:01:42 -05:00
Author
Owner
Copy Link

@CharlesEkkel commented on GitHub (Oct 29, 2022):

I've made a PR for this issue as you can see above ^ I figure the simplest way to deal with this is just to add a validation rule when creating accounts.

<!-- gh-comment-id:1295697727 --> @CharlesEkkel commented on GitHub (Oct 29, 2022): I've made a PR for this issue as you can see above ^ I figure the simplest way to deal with this is just to add a validation rule when creating accounts.
GiteaMirror commented 2026-04-14 17:01:42 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (May 5, 2023):

👋 May I ask: why not? Why should I not be able to have two accounts with the same name if I wanted to?

For example: I might have multiple accounts with the same bank. But these accounts might be of different types: checking, savings, mortgage, investments.

<!-- gh-comment-id:1536750732 --> @MatissJanis commented on GitHub (May 5, 2023): 👋 May I ask: why not? Why should I not be able to have two accounts with the same name if I wanted to? For example: I might have multiple accounts with the same bank. But these accounts might be of different types: checking, savings, mortgage, investments.
GiteaMirror commented 2026-04-14 17:01:43 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (May 6, 2023):

👋 May I ask: why not? Why should I not be able to have two accounts with the same name if I wanted to?

For example: I might have multiple accounts with the same bank. But these accounts might be of different types: checking, savings, mortgage, investments.

How would this work for things like importing? How would you differentiate between the two accounts in a drop down?

If I look in my bank I have my bank called starling but inside that is current account and savings account

Having two accounts in the account register with the same name will become confusing.

<!-- gh-comment-id:1537108634 --> @rich-howell commented on GitHub (May 6, 2023): > 👋 May I ask: why not? Why should I not be able to have two accounts with the same name if I wanted to? > > > > For example: I might have multiple accounts with the same bank. But these accounts might be of different types: checking, savings, mortgage, investments. How would this work for things like importing? How would you differentiate between the two accounts in a drop down? If I look in my bank I have my bank called **starling** but inside that is **current account** and **savings account** Having two accounts in the account register with the same name will become confusing.
GiteaMirror commented 2026-04-14 17:01:44 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (May 6, 2023):

Having two accounts in the account register with the same name will become confusing

Agreed, I name mine “USAA Checking” and “USAA Savings” to disambiguate.

Since people might already have duplicate account names I think we should just block any new attempts to save an account name that’s already used rather than having some preemptive approach.

<!-- gh-comment-id:1537126944 --> @j-f1 commented on GitHub (May 6, 2023): > Having two accounts in the account register with the same name will become confusing Agreed, I name mine “USAA Checking” and “USAA Savings” to disambiguate. Since people might already have duplicate account names I think we should just block any new attempts to save an account name that’s already used rather than having some preemptive approach.
GiteaMirror commented 2026-04-14 17:01:45 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (May 6, 2023):

Ok, you convinced me. For import purposes it does make sense to require unique names so we could map 1:1 (we could also use account iDs for that, but it would be.. quite "clunky" experience).

Should we make this a feature request?

<!-- gh-comment-id:1537222465 --> @MatissJanis commented on GitHub (May 6, 2023): Ok, you convinced me. For import purposes it does make sense to require unique names so we could map 1:1 (we could also use account iDs for that, but it would be.. quite "clunky" experience). Should we make this a feature request?
GiteaMirror commented 2026-04-14 17:01:45 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (May 6, 2023):

Should we make this a feature request?

Or is it a bug?

<!-- gh-comment-id:1537222943 --> @rich-howell commented on GitHub (May 6, 2023): > Should we make this a feature request? Or is it a bug?
GiteaMirror commented 2026-04-14 17:01:45 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (May 27, 2023):

Should we make this a feature request?

Or is it a bug?

Took an executive decision, it is a bug.

<!-- gh-comment-id:1565298019 --> @rich-howell commented on GitHub (May 27, 2023): > > Should we make this a feature request? > > Or is it a bug? Took an executive decision, it is a bug.
GiteaMirror commented 2026-04-14 17:01:46 -05:00
Author
Owner
Copy Link

@Tigatok commented on GitHub (May 18, 2024):

We can handle this on the front-end if we want a quick win, not sure how intense this would be for the backend/at the API level. Let me know if you want me to move to BE.

https://github.com/actualbudget/actual/assets/3906461/80f56440-1b09-4823-bc09-e785e07668b3

<!-- gh-comment-id:2118507898 --> @Tigatok commented on GitHub (May 18, 2024): We can handle this on the front-end if we want a quick win, not sure how intense this would be for the backend/at the API level. Let me know if you want me to move to BE. https://github.com/actualbudget/actual/assets/3906461/80f56440-1b09-4823-bc09-e785e07668b3
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug good first issue user interface
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#14266
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?