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

[Feature] Donut Graph colors should reference specific categories #2419

New Issue
Closed
opened 2026-02-28 20:13:21 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:13:21 -06:00
Owner
Copy Link

Originally created by @SamPlaysKeys on GitHub (Aug 25, 2025).

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?

Feature Request: Category-Based Color Scheme for Circle Graph

Summary:
Implement a color scheme for the circle graph in the finance app that assigns colors based on the category of the expense rather than the percentage of the expense. This enhancement will provide users with a more intuitive and visually coherent representation of their expenses month-to-month.

Current Behavior:
Currently, the circle graph assigns colors to expense segments based on their ranking in the percentage of the total expenses. This can lead to confusion when quickly identifying categories, as color associations can change dynamically with different expense distributions.

Example

Image

Describe your ideal solution to this problem

Proposed Behavior:

  • Assign colors iteratively based on the order of the categories in the budget breakout.
  • Ensure consistency in color association so that each category retains the same color across different months or views.
  • Optionally provide users with the ability to customize these colors through settings for personalization.

Benefits:

  • Enhances user experience by allowing quicker recognition of categories at a glance.
  • Improves overall visual cohesion and intuitiveness of the app's graphical representation of data.
  • Allows users to focus more on analyzing spending habits without needing to decipher changing color schemes.

Teaching and learning

As long as the feature is automatic, no additional training/discovery will be needed.
If the option of color choice per-category is implemented, documentation on the selection/change process for each category's color will be needed.

Originally created by @SamPlaysKeys on GitHub (Aug 25, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? ## Feature Request: Category-Based Color Scheme for Circle Graph **Summary:** Implement a color scheme for the circle graph in the finance app that assigns colors based on the category of the expense rather than the percentage of the expense. This enhancement will provide users with a more intuitive and visually coherent representation of their expenses month-to-month. **Current Behavior:** Currently, the circle graph assigns colors to expense segments based on their ranking in the percentage of the total expenses. This can lead to confusion when quickly identifying categories, as color associations can change dynamically with different expense distributions. ## Example <img width="901" height="447" alt="Image" src="https://github.com/user-attachments/assets/adaf023e-dce3-4e99-ba41-15c4217d0cc8" /> ### Describe your ideal solution to this problem **Proposed Behavior:** - Assign colors iteratively based on the order of the categories in the budget breakout. - Ensure consistency in color association so that each category retains the same color across different months or views. - Optionally provide users with the ability to customize these colors through settings for personalization. **Benefits:** - Enhances user experience by allowing quicker recognition of categories at a glance. - Improves overall visual cohesion and intuitiveness of the app's graphical representation of data. - Allows users to focus more on analyzing spending habits without needing to decipher changing color schemes. ### Teaching and learning As long as the feature is automatic, no additional training/discovery will be needed. If the option of color choice per-category is implemented, documentation on the selection/change process for each category's color will be needed.
GiteaMirror added the featureneeds votes labels 2026-02-28 20:13:21 -06:00
GiteaMirror commented 2026-02-28 20:13:22 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 25, 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 👍!

@github-actions[bot] commented on GitHub (Aug 25, 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-02-28 20:13:22 -06:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Aug 30, 2025):

Thank you for creating this feature request. I've also wished for something like this.

@kcollett commented on GitHub (Aug 30, 2025): Thank you for creating this feature request. I've also wished for something like this.
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#2419
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?