github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #8036] Add a second optional transaction category #117648

New Issue
Closed
opened 2026-06-11 13:05:22 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-06-11 13:05:22 -05:00
Owner
Copy Link

Originally created by @Lucybelle626 on GitHub (Jun 2, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/8036

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?

Hi, I have just started using Actual and would love the ability to add a second category to transactions as a second way to group budget items. Initially I thought grouping categories would work but I would like items in the same category to be able to be categorized differently. For me the second category would be Core spending (i.e., keeping the lights on, base expenses needed to live) vs. Adaptive spending (i.e., nice to have things that could be foregone or given up). I am working on retirement budgeting and figuring out what I need to live vs. what I could do if my projections are successful. I noted a request for sub-category, but this second category would be independent of the first category. Someone mentioned tags, and this could work for what I want, as long as it could be used to filter in the same manner as categories. Thanks for any considerations. I'm so impressed by what I have seen here so far!

Describe your ideal solution to this problem

Ideally this would be a second field right after the existing Category field that is independent of the first.

Teaching and learning

No response

Originally created by @Lucybelle626 on GitHub (Jun 2, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/8036 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Hi, I have just started using Actual and would love the ability to add a second category to transactions as a second way to group budget items. Initially I thought grouping categories would work but I would like items in the same category to be able to be categorized differently. For me the second category would be Core spending (i.e., keeping the lights on, base expenses needed to live) vs. Adaptive spending (i.e., nice to have things that could be foregone or given up). I am working on retirement budgeting and figuring out what I need to live vs. what I could do if my projections are successful. I noted a request for sub-category, but this second category would be independent of the first category. Someone mentioned tags, and this could work for what I want, as long as it could be used to filter in the same manner as categories. Thanks for any considerations. I'm so impressed by what I have seen here so far! ### Describe your ideal solution to this problem Ideally this would be a second field right after the existing Category field that is independent of the first. ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-06-11 13:05:23 -05:00
GiteaMirror commented 2026-06-11 13:05:25 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 2, 2026):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 👍!

<!-- gh-comment-id:4598225723 --> @github-actions[bot] commented on GitHub (Jun 2, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 -->
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
tech-support
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#117648
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?