[Feature]: Automatically set category when adding a transaction to the budget category transaction list #438

Closed
opened 2026-02-28 19:04:18 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @joel-jeremy on GitHub (Jun 19, 2023).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When adding a transaction to a category via category transactions page (the page after clicking a category's spent amount in the budget table), the category is not automatically set to the clicked category.

What error did you receive?

No response

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Chrome

Operating System

Mobile Device

Originally created by @joel-jeremy on GitHub (Jun 19, 2023). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? When adding a transaction to a category via category transactions page (the page after clicking a category's spent amount in the budget table), the category is not automatically set to the clicked category. ### What error did you receive? _No response_ ### Where are you hosting Actual? Fly.io ### What browsers are you seeing the problem on? Chrome ### Operating System Mobile Device
GiteaMirror added the transactionsfeature labels 2026-02-28 19:04:18 -06:00
Author
Owner

@j-f1 commented on GitHub (Jun 20, 2023):

This is a great idea! I’m going to recategorize it as a feature request since this functionality does not exist yet, and you can see that the category is missing by looking at the table.

@j-f1 commented on GitHub (Jun 20, 2023): This is a great idea! I’m going to recategorize it as a feature request since this functionality does not exist yet, and you can see that the category is missing by looking at the table.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 20, 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 (Jun 20, 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 👍! <!-- feature-auto-close-comment -->
Author
Owner

@j-f1 commented on GitHub (Jun 27, 2023):

impersonates bot since it isn’t working for some reason

🎉 This feature has been implemented in #1176 and will be released in the next version. Thanks for sharing your idea! 🎉

@j-f1 commented on GitHub (Jun 27, 2023): *impersonates bot since it isn’t working for some reason* :tada: This feature has been implemented in #1176 and will be released in the next version. Thanks for sharing your idea! :tada:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#438