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

[Feature] Support applying Categorisations to single, single and future, or all Transactions in UI #201

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

Originally created by @rich-howell on GitHub (Jan 22, 2023).

Discussed in https://github.com/actualbudget/actual/discussions/153

Originally posted by winklevos August 6, 2022
When categorizing a transaction, ability to choose
- Apply only to this transaction
- Apply to all future matching transactions
- Apply to all future and past matching transaction

Originally created by @rich-howell on GitHub (Jan 22, 2023). ### Discussed in https://github.com/actualbudget/actual/discussions/153 <div type='discussions-op-text'> <sup>Originally posted by **winklevos** August 6, 2022</sup> When categorizing a transaction, ability to choose - Apply only to this transaction - Apply to all future matching transactions - Apply to all future and past matching transaction</div>
GiteaMirror added the user interfaceneeds votesfeaturehelp wanted labels 2026-02-28 18:52:12 -06:00
GiteaMirror commented 2026-02-28 18:52:13 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Feb 16, 2023):

This is an interesting proposal and definitely one that I would support. Oftentimes I find myself having to manually categorize transactions from the same payee, because somehow the automatic-categorization logic just isn't working for it..

The ability to manually tweak this during transaction creation is an interesting idea.

From a UX perspective this might be a tricky problem because we don't want to always pop-open a modal when creating a transaction. This functionality should be subtle and elegant.

@MatissJanis commented on GitHub (Feb 16, 2023): This is an interesting proposal and definitely one that I would support. Oftentimes I find myself having to manually categorize transactions from the same payee, because somehow the automatic-categorization logic just isn't working for it.. The ability to manually tweak this __during__ transaction creation is an interesting idea. From a UX perspective this might be a tricky problem because we don't want to always pop-open a modal when creating a transaction. This functionality should be subtle and elegant.
GiteaMirror commented 2026-02-28 18:52:13 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 1, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 (May 1, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!
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 help wanted needs votes 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#201
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?