github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 15:12:35 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #6377] [Bug]: In transaction list, editing payee and clicking 'merge and edit rule' does not work if not renaming in the future #16956

New Issue
Closed
opened 2026-04-14 19:55:19 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-14 19:55:19 -05:00
Owner
Copy Link

Originally created by @tcrasset on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6377

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When in the transaction list, we ovewrite a payee name with a new same and hit enter, the modal pops up asking us if we want to merge it.

If you uncheck the box 'Automatically rename these payees in the future', and you hit the 'Merge and edit rule button', it doesn't propose you to modify a rule.

Not sure if that is the expected outcome (I guess no rule will be created when the box is unchecked, leading to no rule being able to be edited).

I guess we should either remove the button if you uncheck the box (because no rule will be created), or just have the two buttons and not the checkbox? It's confusing to have both.

How can we reproduce the issue?

See above.

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @tcrasset on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6377 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When in the transaction list, we ovewrite a payee name with a new same and hit enter, the modal pops up asking us if we want to merge it. If you uncheck the box 'Automatically rename these payees in the future', and you hit the 'Merge and edit rule button', it doesn't propose you to modify a rule. Not sure if that is the expected outcome (I guess no rule will be created when the box is unchecked, leading to no rule being able to be edited). I guess we should either remove the button if you uncheck the box (because no rule will be created), or just have the two buttons and not the checkbox? It's confusing to have both. ### How can we reproduce the issue? See above. ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the rulestransactionsgood first issuebug labels 2026-04-14 19:55:20 -05:00
GiteaMirror commented 2026-04-14 19:55:22 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 12, 2025):

I think the issue is because no rule gets created if you unceck the rename in the future option. So no rule, no rule to edit. That button probably shouldn't be there if the option is unchecked

Oh yep, you already noted that.

<!-- gh-comment-id:3647112142 --> @youngcw commented on GitHub (Dec 12, 2025): I think the issue is because no rule gets created if you unceck the rename in the future option. So no rule, no rule to edit. That button probably shouldn't be there if the option is unchecked Oh yep, you already noted that.
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 bug good first issue rules transactions
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#16956
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?