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

[GH-ISSUE #6108] [Feature] Merge Payees should ask for confirmation #116985

New Issue
Closed
opened 2026-06-11 10:58:18 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-06-11 10:58:18 -05:00
Owner
Copy Link

Originally created by @AsgerMogensen on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6108

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

When merging several groups of payees, it can easily happen, that you forget to deselect payee A before merging B1 and B2. In this case they will all be merged into one and if you don't notice it immediately and press ctrl+z you will have to find every single transaction with the original payee to fix it.

It happened to me, where I didn't press ctrl+z because I searched for "B" before realising, that it had been merged with A. Because I searched it was too late to go back and i had to fix every transaction manually.

Describe your ideal solution to this problem

The ideal solution would be a modal that pops up and asks "Would you like to merge the payees A, B1 and B2?". This would make it more obvious, that you are merging the wrong categories.

Teaching and learning

No response

Originally created by @AsgerMogensen on GitHub (Nov 10, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6108 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? When merging several groups of payees, it can easily happen, that you forget to deselect payee A before merging B1 and B2. In this case they will all be merged into one and if you don't notice it immediately and press ctrl+z you will have to find every single transaction with the original payee to fix it. It happened to me, where I didn't press ctrl+z because I searched for "B" before realising, that it had been merged with A. Because I searched it was too late to go back and i had to fix every transaction manually. ### Describe your ideal solution to this problem The ideal solution would be a modal that pops up and asks "Would you like to merge the payees A, B1 and B2?". This would make it more obvious, that you are merging the wrong categories. ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-06-11 10:58:18 -05:00
GiteaMirror commented 2026-06-11 10:58:22 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Nov 11, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:3519146136 --> @matt-fidd commented on GitHub (Nov 11, 2025): ✨ Thanks for sharing your idea! ✨ This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍!
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 feature
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#116985
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?