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

[PR #2786] [MERGED] Match on amount when creating a rule from a transaction #18873

New Issue
Closed
opened 2026-04-14 20:53:29 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-14 20:53:29 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/2786
Author: @jfdoming
Created: 5/21/2024
Status: ✅ Merged
Merged: 5/22/2024
Merged by: @youngcw

Base: master ← Head: jfdoming/more-specific-rule-creation

📝 Commits (4)

  • af13666 Use amount when creating a rule from a transaction
  • 4120505 Merge branch 'master' into jfdoming/more-specific-rule-creation
  • a7ec17e Add release notes
  • b98078b Merge branch 'master' into jfdoming/more-specific-rule-creation

📊 Changes

2 files changed (+13 additions, -1 deletions)

View changed files

📝 packages/desktop-client/src/components/accounts/Account.jsx (+7 -1)
➕ upcoming-release-notes/2786.md (+6 -0)

📄 Description

Updates the "Create rule" action in the transactions table to be slightly more specific when matching. This should be useful in general for matching regular transactions (folks can always delete the additional condition). I also considered adding a condition for the account but decided that wouldn't be as useful (feel free to push back!).

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/2786 **Author:** [@jfdoming](https://github.com/jfdoming) **Created:** 5/21/2024 **Status:** ✅ Merged **Merged:** 5/22/2024 **Merged by:** [@youngcw](https://github.com/youngcw) **Base:** `master` ← **Head:** `jfdoming/more-specific-rule-creation` --- ### 📝 Commits (4) - [`af13666`](https://github.com/actualbudget/actual/commit/af136662698f62d6f5b938f5f5ffa6e1dc93f6ed) Use amount when creating a rule from a transaction - [`4120505`](https://github.com/actualbudget/actual/commit/4120505243e00f71cc9a5b0a5b0c650dfcfbcd2e) Merge branch 'master' into jfdoming/more-specific-rule-creation - [`a7ec17e`](https://github.com/actualbudget/actual/commit/a7ec17eceb0b8b49209e209d7a1639ff234ecc5a) Add release notes - [`b98078b`](https://github.com/actualbudget/actual/commit/b98078b4b5d3e74d718ad2db6e4ce33dc0b3f097) Merge branch 'master' into jfdoming/more-specific-rule-creation ### 📊 Changes **2 files changed** (+13 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/accounts/Account.jsx` (+7 -1) ➕ `upcoming-release-notes/2786.md` (+6 -0) </details> ### 📄 Description Updates the "Create rule" action in the transactions table to be slightly more specific when matching. This should be useful in general for matching regular transactions (folks can always delete the additional condition). I also considered adding a condition for the account but decided that wouldn't be as useful (feel free to push back!). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-14 20:53:29 -05:00
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 pull-request
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#18873
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?