github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Feature] Consistent colors in custom reports #2139

New Issue
Closed
opened 2026-02-28 20:04:26 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:04:26 -06:00
Owner
Copy Link

Originally created by @vbrodeur on GitHub (May 18, 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?

When I look at custom reports, the color for a given category/group/payee/account is not consistent across all reports.
I think it would facilitate the readability of the reports if a color always referred to the same category. Image
When I first looked at my reports I was confused until I hovered the categories to see the different names on the same content.

Describe your ideal solution to this problem

I'm not familiar with the code base so these might not make sense.
To simplify the description, I use categories to refer to any content displayed in custom reports (categories, groups, payees or accounts)

  1. (preferred solution) Currently the categories are colored in order of size in the data relevant to the report. They could instead be ordered by size in all the data, by the same order in which they appear in the "Budget" tab, or any other order that is consistent across all reports and simple/quick to access. With this, colors might still change from time to time when the ordering of categories changes but would still be consistent across reports.

  2. Associating colors to categories could also be done once (ie at creation of a category?) and saved persistently. This could be done with a predefined list of colors similar to what we have now or with a color-selector. This solution requires significantly more time than the first (implementing the color-selector, saving the preferred color for each category, UI changes to add an option to open the selector, etc). Unless a color-selector or category having a color is something we want to use else where, I would go for the first solution.

Teaching and learning

Depends on the selected solution.

  1. N/A, (maybe a bit of doc for the devs)
  2. a short description of the feature in the doc for "custom reports"
Originally created by @vbrodeur on GitHub (May 18, 2025). ### 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? When I look at custom reports, the color for a given category/group/payee/account is not consistent across all reports. I think it would facilitate the readability of the reports if a color always referred to the same category. ![Image](https://github.com/user-attachments/assets/936ad9b4-9ffa-44bc-a032-521134dec939) When I first looked at my reports I was confused until I hovered the categories to see the different names on the same content. ### Describe your ideal solution to this problem I'm not familiar with the code base so these might not make sense. To simplify the description, I use categories to refer to any content displayed in custom reports (categories, groups, payees or accounts) 1. (preferred solution) Currently the categories are colored in order of size in the data relevant to the report. They could instead be ordered by size in all the data, by the same order in which they appear in the "Budget" tab, or any other order that is consistent across all reports and simple/quick to access. With this, colors might still change from time to time when the ordering of categories changes but would still be consistent across reports. 2. Associating colors to categories could also be done once (ie at creation of a category?) and saved persistently. This could be done with a predefined list of colors similar to what we have now or with a color-selector. This solution requires significantly more time than the first (implementing the color-selector, saving the preferred color for each category, UI changes to add an option to open the selector, etc). Unless a color-selector or category having a color is something we want to use else where, I would go for the first solution. ### Teaching and learning Depends on the selected solution. 1. N/A, (maybe a bit of doc for the devs) 2. a short description of the feature in the doc for "custom reports"
GiteaMirror added the needs votesfeature labels 2026-02-28 20:04:26 -06:00
GiteaMirror commented 2026-02-28 20:04:27 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 18, 2025):

✨ 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 (May 18, 2025): :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 -->
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#2139
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?