github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 04:02:38 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] sub-categories (or category tags) #1360

New Issue
Closed
opened 2026-02-28 19:41:36 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-02-28 19:41:36 -06:00
Owner
Copy Link

Originally created by @leonardo091800 on GitHub (Aug 27, 2024).

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,
Id'love to be able to have sub-categories and see them in the report as additional charts.

For example:
Categories:

  1. food
    a. restaurants
    b. groceries
  2. travel
    a. accomodations
    b. car
    • fuel
    • taxes
    • mortgages
  3. house

Is it possible?
And is this the correct repo to ask or should have I opened the request on the actual-server repo?

Describe your ideal solution to this problem

redis syntax

make it could be possible to insert in each payment an ordered list of the categories and subcategories

payment:

  • date
  • payee
  • category:
    • mainCategory
    • subcategory1
    • subcategory2
    • ...

and then create charts of all categories[0] and categories[1] etc.

sql syntax

or in sql maybe add a reference to the subcategory:
category table:

  • id | name
  • 01 | mainCategory
  • 02 | subcategory1
  • 03 | subcategory2

subcategories table:

  • id_main | id_sub
  • 01 | 02
  • 03 | 02

payments table:

  • id | date | payee | category
  • xx | xx/xx/xx | xxxxxx | 03

and then create charts of

  • all items where category not in subcategories table
  • all items that have the same categoy id in id_main

Teaching and learning

It will extremely help in micromanaging the finances of users

Originally created by @leonardo091800 on GitHub (Aug 27, 2024). ### 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, Id'love to be able to have sub-categories and see them in the report as additional charts. For example: Categories: 1. food a. restaurants b. groceries 3. travel a. accomodations b. car * fuel * taxes * mortgages 5. house Is it possible? And is this the correct repo to ask or should have I opened the request on the actual-server repo? ### Describe your ideal solution to this problem # redis syntax make it could be possible to insert in each payment an ordered list of the categories and subcategories payment: - date - payee - category: - mainCategory - subcategory1 - subcategory2 - ... and then create charts of all categories[0] and categories[1] etc. --- # sql syntax or in sql maybe add a reference to the subcategory: category table: - id | name - 01 | mainCategory - 02 | subcategory1 - 03 | subcategory2 subcategories table: - id_main | id_sub - 01 | 02 - 03 | 02 payments table: - id | date | payee | category - xx | xx/xx/xx | xxxxxx | 03 and then create charts of - all items where category not in subcategories table - all items that have the same categoy id in id_main ### Teaching and learning It will extremely help in micromanaging the finances of users
GiteaMirror added the needs votesfeature labels 2026-02-28 19:41:36 -06:00
GiteaMirror commented 2026-02-28 19:41:37 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 27, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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 (Aug 27, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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 -->
GiteaMirror commented 2026-02-28 19:41:37 -06:00
Author
Owner
Copy Link

@CrazyKidJack commented on GitHub (Sep 14, 2024):

I gave this a👍. I think it could equally be called "super groups" if someone is hung up on the idea that "categories" should be the lowest level thing.

Additionally, I'd love to not only see group > category > sub-category... or super group > group > category... but generally speaking I'd like to see infinitely nestable grouping.

@CrazyKidJack commented on GitHub (Sep 14, 2024): I gave this a👍. I think it could equally be called "super groups" if someone is hung up on the idea that "categories" should be the lowest level thing. Additionally, I'd love to not only see group > category > sub-category... or super group > group > category... but generally speaking I'd like to see infinitely nestable grouping.
GiteaMirror commented 2026-02-28 19:41:38 -06:00
Author
Owner
Copy Link

@CrazyKidJack commented on GitHub (Sep 14, 2024):

Maybe a duplicate of: https://github.com/actualbudget/actual/issues/1320

@CrazyKidJack commented on GitHub (Sep 14, 2024): Maybe a duplicate of: https://github.com/actualbudget/actual/issues/1320
GiteaMirror commented 2026-02-28 19:41:38 -06:00
Author
Owner
Copy Link

@pwinnski commented on GitHub (Nov 22, 2024):

I'm glad someone has already suggested "infinitely nestable grouping" so that I don't sound crazy when I say this seems like a terrible idea. If one level of grouping isn't enough, why would two be enough? Won't there then be a request for three? Then four? It's a UI and UX nightmare in the making.

If the goal is to rollup a subset of categories into a collection, separate from the group to which it belongs, I suggest that reports/charts be enhanced to work better with tags, or have an option to combine categories on a report which begin with a common string. But please, let's not open up such an easy way to destroy UX on the budget screen!

@pwinnski commented on GitHub (Nov 22, 2024): I'm glad someone has already suggested "infinitely nestable grouping" so that I don't sound crazy when I say this seems like a terrible idea. If one level of grouping isn't enough, why would two be enough? Won't there then be a request for three? Then four? It's a UI and UX nightmare in the making. If the goal is to rollup a subset of categories into a collection, separate from the group to which it belongs, I suggest that reports/charts be enhanced to work better with tags, or have an option to combine categories on a report which begin with a common string. But please, let's not open up such an easy way to destroy UX on the budget screen!
GiteaMirror commented 2026-02-28 19:41:38 -06:00
Author
Owner
Copy Link

@pboushy commented on GitHub (Jan 14, 2025):

I'd want to allow multiple levels of nesting of categories. IMO at a minimum, there should be 3 levels.

A great example of that is paystubs:

pay
    taxable
        salary
        bonus
    tax
        federal
        state
     after-tax
        retirement
@pboushy commented on GitHub (Jan 14, 2025): I'd want to allow multiple levels of nesting of categories. IMO at a minimum, there should be 3 levels. A great example of that is paystubs: ``` pay taxable salary bonus tax federal state after-tax retirement ```
GiteaMirror commented 2026-02-28 19:41:39 -06:00
Author
Owner
Copy Link

@aGitForEveryone commented on GitHub (Aug 21, 2025):

WIP: #5268

@aGitForEveryone commented on GitHub (Aug 21, 2025): WIP: #5268
GiteaMirror commented 2026-02-28 19:41:39 -06:00
Author
Owner
Copy Link

@HoniSanders commented on GitHub (Jan 8, 2026):

duplicate of https://github.com/actualbudget/actual/issues/1320

@HoniSanders commented on GitHub (Jan 8, 2026): duplicate of https://github.com/actualbudget/actual/issues/1320
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 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#1360
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?