github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-11 09:38:37 -05:00
Code Issues 1.6k Packages Projects Releases 57 Wiki Activity

[GH-ISSUE #5633] [Feature] Ability to create report widgets splitting category with tags in notes #28215

New Issue
Closed
opened 2026-04-18 04:53:17 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-18 04:53:17 -05:00
Owner
Copy Link

Originally created by @binarygituser on GitHub (Aug 26, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5633

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?

How to split a categoryPie in reports according to tags ? For Example, I have 4 different tags in the category (Shopping) that is part of FunMoney Group. I want to create a pie that shows how much each tag has in expenses for the month. Hierarchy is FunMoney (group) -> Shopping (category) -> kid1/kid2/Parent1/Parent2 (Tags). I want to see a pie that is split according to expenses in each tag. The way report is structured now, it needs to know what tag I am filtering upon (query) and then it shows how much money was spent with notes containing that Tag. Any other way to achieve what I want ?

Describe your ideal solution to this problem

We should be able to create a widget for a category that is split acccording to all notes that have tags without having to setup individual queries for each tag.

Teaching and learning

No response

Originally created by @binarygituser on GitHub (Aug 26, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5633 ### 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? How to split a categoryPie in reports according to tags ? For Example, I have 4 different tags in the category (Shopping) that is part of FunMoney Group. I want to create a pie that shows how much each tag has in expenses for the month. Hierarchy is FunMoney (group) -> Shopping (category) -> kid1/kid2/Parent1/Parent2 (Tags). I want to see a pie that is split according to expenses in each tag. The way report is structured now, it needs to know what tag I am filtering upon (query) and then it shows how much money was spent with notes containing that Tag. Any other way to achieve what I want ? ### Describe your ideal solution to this problem We should be able to create a widget for a category that is split acccording to all notes that have tags without having to setup individual queries for each tag. ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-18 04:53:17 -05:00
GiteaMirror commented 2026-04-18 04:53:19 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 26, 2025):

✨ 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:3225033797 --> @github-actions[bot] commented on GitHub (Aug 26, 2025): :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 -->
GiteaMirror commented 2026-04-18 04:53:19 -05:00
Author
Owner
Copy Link

@tomasgriffin commented on GitHub (Aug 27, 2025):

I've considered implementing this although tags introduce a many-to-many problem that make it difficult to report on. How would you propose you deal with transactions sharing multiple tags?

Example:

Transaction 1 - £-10.00 (#one)
Transaction 2 - £-10.00 (#two)
Transaction 3 - £-10.00 (#one, #two)

When I split the report based on tag, to which tag do I assign Transaction 3's amount?

As far as I see it there are 3 options:

  1. Double count the amount (#one £-20.00, #two £-20.00)
  2. Split the amount (#one £-15.00, #two £-15.00)
  3. Treat the tags as unique sets and split into a separate group (#one £-10.00, #two £-10.00, #one, #two £-10.00)
<!-- gh-comment-id:3227973692 --> @tomasgriffin commented on GitHub (Aug 27, 2025): I've considered implementing this although tags introduce a many-to-many problem that make it difficult to report on. How would you propose you deal with transactions sharing multiple tags? Example: Transaction 1 - £-10.00 (`#one`) Transaction 2 - £-10.00 (`#two`) Transaction 3 - £-10.00 (`#one`, `#two`) When I split the report based on tag, to which tag do I assign Transaction 3's amount? As far as I see it there are 3 options: 1. Double count the amount (`#one` £-20.00, `#two` £-20.00) 2. Split the amount (`#one` £-15.00, `#two` £-15.00) 3. Treat the tags as unique sets and split into a separate group (`#one` £-10.00, `#two` £-10.00, `#one, #two` £-10.00)
GiteaMirror commented 2026-04-18 04:53:20 -05:00
Author
Owner
Copy Link

@binarygituser commented on GitHub (Aug 27, 2025):

I've considered implementing this although tags introduce a many-to-many problem that make it difficult to report on. How would you propose you deal with transactions sharing multiple tags?

Example:

Transaction 1 - £-10.00 (#one) Transaction 2 - £-10.00 (#two) Transaction 3 - £-10.00 (#one, #two)

When I split the report based on tag, to which tag do I assign Transaction 3's amount?

As far as I see it there are 3 options:

  1. Double count the amount (#one £-20.00, #two £-20.00)
  2. Split the amount (#one £-15.00, #two £-15.00)
  3. Treat the tags as unique sets and split into a separate group (#one £-10.00, #two £-10.00, #one, #two £-10.00)

In my use case, i imagined I would simply split the transaction and assign only one tag per split although keeping the same category for both splits. This adds an additional step to split the transaction, but helps show reporting better. I know actual does not limit 1 tag per transaction, but i tend to have one tag per transaction and split if reqd.
Having said that, among the options you suggest, number 3 makes the most sense to me !

<!-- gh-comment-id:3228697699 --> @binarygituser commented on GitHub (Aug 27, 2025): > I've considered implementing this although tags introduce a many-to-many problem that make it difficult to report on. How would you propose you deal with transactions sharing multiple tags? > > Example: > > Transaction 1 - £-10.00 (`#one`) Transaction 2 - £-10.00 (`#two`) Transaction 3 - £-10.00 (`#one`, `#two`) > > When I split the report based on tag, to which tag do I assign Transaction 3's amount? > > As far as I see it there are 3 options: > > 1. Double count the amount (`#one` £-20.00, `#two` £-20.00) > 2. Split the amount (`#one` £-15.00, `#two` £-15.00) > 3. Treat the tags as unique sets and split into a separate group (`#one` £-10.00, `#two` £-10.00, `#one, #two` £-10.00) In my use case, i imagined I would simply split the transaction and assign only one tag per split although keeping the same category for both splits. This adds an additional step to split the transaction, but helps show reporting better. I know actual does not limit 1 tag per transaction, but i tend to have one tag per transaction and split if reqd. Having said that, among the options you suggest, number 3 makes the most sense to me !
GiteaMirror commented 2026-04-18 04:53:20 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jan 22, 2026):

duplicate #3130

<!-- gh-comment-id:3787030438 --> @youngcw commented on GitHub (Jan 22, 2026): duplicate #3130
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
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#28215
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?