github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Merge Payees should ask for Automatic Payee renaming rule #1660

New Issue
Closed
opened 2026-02-28 19:50:06 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:50:06 -06:00
Owner
Copy Link

Originally created by @Teifun2 on GitHub (Dec 10, 2024).

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 in the Payees Management Tab there is the handy feature to Merge Payees.
This combines all rules onto one Payee.
Additionally you can rename Payees there.

However if you rename a payee or merge payees there is no way to create the payee renaming rules.

This is different behaviour than in the Budget overview, where you can rename/change a payee. And if the original name was the last of its kind it will ask if the system should create the neccesarry "renaming" rule.

This behaviour is also mentioned here:
https://actualbudget.org/docs/budgeting/rules/#automatic-rules

It would be nice if this popup would also appear in the payee overview if payees are merged or renamed!

Describe your ideal solution to this problem

Provide the same automatic renaming popup as currently available in the budget page when renaming the last case.
image

Teaching and learning

The feature already exists on a different screen, and is described in the Actual Documentation.

No further discovery assistance is needed.

Originally created by @Teifun2 on GitHub (Dec 10, 2024). ### 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 in the Payees Management Tab there is the handy feature to Merge Payees. This combines all rules onto one Payee. Additionally you can rename Payees there. However if you rename a payee or merge payees there is no way to create the payee renaming rules. This is different behaviour than in the Budget overview, where you can rename/change a payee. And if the original name was the last of its kind it will ask if the system should create the neccesarry "renaming" rule. This behaviour is also mentioned here: https://actualbudget.org/docs/budgeting/rules/#automatic-rules It would be nice if this popup would also appear in the payee overview if payees are merged or renamed! ### Describe your ideal solution to this problem Provide the same automatic renaming popup as currently available in the budget page when renaming the last case. ![image](https://github.com/user-attachments/assets/9789ea7c-3f34-4b9a-8eab-c738942cbd34) ### Teaching and learning The feature already exists on a different screen, and is described in the Actual Documentation. No further discovery assistance is needed.
GiteaMirror added the needs votesfeature labels 2026-02-28 19:50:06 -06:00
GiteaMirror commented 2026-02-28 19:50:07 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 10, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!

@github-actions[bot] commented on GitHub (Dec 10, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-02-28 19:50:08 -06:00
Author
Owner
Copy Link

@Teifun2 commented on GitHub (Jan 12, 2025):

Is this something that would get approved? I would be willing to try and implement this myself!

@Teifun2 commented on GitHub (Jan 12, 2025): Is this something that would get approved? I would be willing to try and implement this myself!
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
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#1660
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?