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

[GH-ISSUE #730] [Feature] Custom Reports #14527

New Issue
Closed
opened 2026-04-14 17:16:37 -05:00 by GiteaMirror · 21 comments
GiteaMirror commented 2026-04-14 17:16:37 -05:00
Owner
Copy Link

Originally created by @shahzadali84 on GitHub (Mar 6, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/730

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?

Hello,

I have just started using Actual. However I noticed that the reports are way too simple and therefore I would like to add some custom reports and use it for my personal use.

If I find it useful I can also add it to the community for wider audience.

I have actual-server checked out locally but I wonder where is the Actual code and how actual-server is getting Actual app? My question is that if I add some custom report, how can I use it just locally for testing and then deploy it for wider audience?

Describe your ideal solution to this problem

Add reports similar to YNAB

Teaching and learning

n/a

Originally created by @shahzadali84 on GitHub (Mar 6, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/730 ### 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? Hello, I have just started using Actual. However I noticed that the reports are way too simple and therefore I would like to add some custom reports and use it for my personal use. If I find it useful I can also add it to the community for wider audience. I have actual-server checked out locally but I wonder where is the Actual code and how actual-server is getting Actual app? My question is that if I add some custom report, how can I use it just locally for testing and then deploy it for wider audience? ### Describe your ideal solution to this problem Add reports similar to YNAB ### Teaching and learning n/a
GiteaMirror added the reportsfeature labels 2026-04-14 17:16:37 -05:00
GiteaMirror commented 2026-04-14 17:16:39 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Mar 6, 2023):

Thank you - I'm just a user not a developer but my big wish would be for an income and expenses account!

<!-- gh-comment-id:1456657084 --> @Kidglove57 commented on GitHub (Mar 6, 2023): Thank you - I'm just a user not a developer but my big wish would be for an income and expenses account!
GiteaMirror commented 2026-04-14 17:16:39 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 6, 2023):

Hi! We’d love to have better reports in the app.

I have actual-server checked out locally but I wonder where is the Actual code and how actual-server is getting Actual app? My question is that if I add some custom report, how can I use it just locally for testing and then deploy it for wider audience?

The code for the frontend (the Actual app you see) is in this repo, and the syncing server is in the actual-server repo. Once you run yarn install and yarn start:browser in this repo your browser should open and you should be able to make changes and refresh to see the results. You can also connect that instance of Actual to your local server if you want to test with your real data (although I recommend loading from a backup instead so that you don’t get your budget messed up by a bug).

<!-- gh-comment-id:1456693663 --> @j-f1 commented on GitHub (Mar 6, 2023): Hi! We’d love to have better reports in the app. > I have actual-server checked out locally but I wonder where is the Actual code and how actual-server is getting Actual app? My question is that if I add some custom report, how can I use it just locally for testing and then deploy it for wider audience? The code for the frontend (the Actual app you see) is in this repo, and the syncing server is in the actual-server repo. Once you run `yarn install` and `yarn start:browser` in this repo your browser should open and you should be able to make changes and refresh to see the results. You can also connect that instance of Actual to your local server if you want to test with your real data (although I recommend loading from a backup instead so that you don’t get your budget messed up by a bug).
GiteaMirror commented 2026-04-14 17:16:40 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Mar 6, 2023):

Hey,

We have an issue #507 here with some report ideas in.

Cheers
Rich

<!-- gh-comment-id:1456741574 --> @rich-howell commented on GitHub (Mar 6, 2023): Hey, We have an issue #507 here with some report ideas in. Cheers Rich
GiteaMirror commented 2026-04-14 17:16:41 -05:00
Author
Owner
Copy Link

@shahzadali84 commented on GitHub (Mar 7, 2023):

Are there steps to setup the Actual repo locally? I cloned the repo but getting tons of errors when try to do "yarn install" and "yarn start:browser"

<!-- gh-comment-id:1457370786 --> @shahzadali84 commented on GitHub (Mar 7, 2023): > Are there steps to setup the Actual repo locally? I cloned the repo but getting tons of errors when try to do "yarn install" and "yarn start:browser"
GiteaMirror commented 2026-04-14 17:16:41 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 7, 2023):

Which errors are you getting?

<!-- gh-comment-id:1457507380 --> @j-f1 commented on GitHub (Mar 7, 2023): Which errors are you getting?
GiteaMirror commented 2026-04-14 17:16:41 -05:00
Author
Owner
Copy Link

@shahzadali84 commented on GitHub (Mar 8, 2023):

Which errors are you getting?

File attached with errors copied
errors.txt

<!-- gh-comment-id:1459108851 --> @shahzadali84 commented on GitHub (Mar 8, 2023): > Which errors are you getting? File attached with errors copied [errors.txt](https://github.com/actualbudget/actual/files/10915374/errors.txt)
GiteaMirror commented 2026-04-14 17:16:42 -05:00
Author
Owner
Copy Link

@carkom commented on GitHub (Mar 8, 2023):

FYI, I've done a lot of what you're looking for. Just submitted PR #731

<!-- gh-comment-id:1459133363 --> @carkom commented on GitHub (Mar 8, 2023): FYI, I've done a lot of what you're looking for. Just submitted PR #731
GiteaMirror commented 2026-04-14 17:16:43 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 8, 2023):

File attached with errors copied

Thanks! Most of that looks ok, the only one that sticks out to me is this one:

➤ YN0009: │ actual@workspace:. couldn't be built successfully (exit code 127, logs can be found here: C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log)

The file at C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log should have more details — patch-package is probably failing but I’m not sure why that would be happening.

<!-- gh-comment-id:1459341900 --> @j-f1 commented on GitHub (Mar 8, 2023): > File attached with errors copied Thanks! Most of that looks ok, the only one that sticks out to me is this one: ``` ➤ YN0009: │ actual@workspace:. couldn't be built successfully (exit code 127, logs can be found here: C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log) ``` The file at `C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log` should have more details — `patch-package` is probably failing but I’m not sure why that would be happening.
GiteaMirror commented 2026-04-14 17:16:43 -05:00
Author
Owner
Copy Link

@shahzadali84 commented on GitHub (Mar 9, 2023):

File attached with errors copied

Thanks! Most of that looks ok, the only one that sticks out to me is this one:

➤ YN0009: │ actual@workspace:. couldn't be built successfully (exit code 127, logs can be found here: C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log)

The file at C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log should have more details — patch-package is probably failing but I’m not sure why that would be happening.

The following is from the logs that got created.

# This file contains the result of Yarn building a package (actual@workspace:.)
# Script name: postinstall

'rm' is not recognized as an internal or external command,
operable program or batch file.
command not found: rm
<!-- gh-comment-id:1461184383 --> @shahzadali84 commented on GitHub (Mar 9, 2023): > > File attached with errors copied > > Thanks! Most of that looks ok, the only one that sticks out to me is this one: > > ``` > ➤ YN0009: │ actual@workspace:. couldn't be built successfully (exit code 127, logs can be found here: C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log) > ``` > > The file at `C:\Users\Shahzad\AppData\Local\Temp\xfs-6f34b1b0\build.log` should have more details — `patch-package` is probably failing but I’m not sure why that would be happening. The following is from the logs that got created. ``` # This file contains the result of Yarn building a package (actual@workspace:.) # Script name: postinstall 'rm' is not recognized as an internal or external command, operable program or batch file. command not found: rm ```
GiteaMirror commented 2026-04-14 17:16:44 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 9, 2023):

Thanks! That helps a lot — opened #733 which should fix that issue once merged.

<!-- gh-comment-id:1461285963 --> @j-f1 commented on GitHub (Mar 9, 2023): Thanks! That helps a lot — opened #733 which should fix that issue once merged.
GiteaMirror commented 2026-04-14 17:16:44 -05:00
Author
Owner
Copy Link

@shahzadali84 commented on GitHub (Mar 9, 2023):

Thanks! That helps a lot — opened #733 which should fix that issue once merged.

Thanks, I was able to complete the yarn install step. However I noticed errors while executing yarn start:browser command

E:\actual-server\actual>yarn start:browser
'sh' is not recognized as an internal or external command,
operable program or batch file.
'bash' is not recognized as an internal or external command,
operable program or batch file.
ERROR: "start:browser-frontend" exited with 1.

E:\actual-server\actual>yarn start:browser-frontend
'sh' is not recognized as an internal or external command,
operable program or batch file.

Any help would be appreciated! Thanks in advance.

<!-- gh-comment-id:1462214370 --> @shahzadali84 commented on GitHub (Mar 9, 2023): > Thanks! That helps a lot — opened #733 which should fix that issue once merged. Thanks, I was able to complete the yarn install step. However I noticed errors while executing yarn start:browser command **E:\actual-server\actual>yarn start:browser** 'sh' is not recognized as an internal or external command, operable program or batch file. 'bash' is not recognized as an internal or external command, operable program or batch file. ERROR: "start:browser-frontend" exited with 1. **E:\actual-server\actual>yarn start:browser-frontend** 'sh' is not recognized as an internal or external command, operable program or batch file. Any help would be appreciated! Thanks in advance.
GiteaMirror commented 2026-04-14 17:16:44 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 9, 2023):

Hm ok, would you be able to try again using WSL? It seems like we don’t really support developing directly on Windows at this point (although that is definitely something we should work towards!)

<!-- gh-comment-id:1462223417 --> @j-f1 commented on GitHub (Mar 9, 2023): Hm ok, would you be able to try again using WSL? It seems like we don’t really support developing directly on Windows at this point (although that is definitely something we should work towards!)
GiteaMirror commented 2026-04-14 17:16:45 -05:00
Author
Owner
Copy Link

@shahzadali84 commented on GitHub (Mar 12, 2023):

Hm ok, would you be able to try again using WSL? It seems like we don’t really support developing directly on Windows at this point (although that is definitely something we should work towards!)

Tried with WSL and following is the output. Not sure if I missed anything.

/mnt/e/actual-server/actual$ sudo yarn start:browser
events.js:291
throw er; // Unhandled 'error' event
^

Error: spawn ./bin/watch-browser EACCES
at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
at onErrorNT (internal/child_process.js:470:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12)
at onErrorNT (internal/child_process.js:470:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: 'EACCES',
code: 'EACCES',
syscall: 'spawn ./bin/watch-browser',
path: './bin/watch-browser',
spawnargs: []
}
ERROR: "start:browser-frontend" exited with 1.

<!-- gh-comment-id:1465081174 --> @shahzadali84 commented on GitHub (Mar 12, 2023): > Hm ok, would you be able to try again using WSL? It seems like we don’t really support developing directly on Windows at this point (although that is definitely something we should work towards!) Tried with WSL and following is the output. Not sure if I missed anything. **/mnt/e/actual-server/actual$ sudo yarn start:browser** events.js:291 throw er; // Unhandled 'error' event ^ Error: spawn ./bin/watch-browser EACCES at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19) at onErrorNT (internal/child_process.js:470:16) at processTicksAndRejections (internal/process/task_queues.js:84:21) Emitted 'error' event on ChildProcess instance at: at Process.ChildProcess._handle.onexit (internal/child_process.js:274:12) at onErrorNT (internal/child_process.js:470:16) at processTicksAndRejections (internal/process/task_queues.js:84:21) { errno: 'EACCES', code: 'EACCES', syscall: 'spawn ./bin/watch-browser', path: './bin/watch-browser', spawnargs: [] } ERROR: "start:browser-frontend" exited with 1.
GiteaMirror commented 2026-04-14 17:16:45 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 12, 2023):

You may have to do chmod +x packages/desktop-client/bin/watch-browser. My guess is that when you first cloned the repo the execute permissions weren’t set up properly by Git.

<!-- gh-comment-id:1465236199 --> @j-f1 commented on GitHub (Mar 12, 2023): You may have to do `chmod +x packages/desktop-client/bin/watch-browser`. My guess is that when you first cloned the repo the execute permissions weren’t set up properly by Git.
GiteaMirror commented 2026-04-14 17:16:46 -05:00
Author
Owner
Copy Link

@shall0pass commented on GitHub (Mar 12, 2023):

I may be ignorant here, but does building in Wsl work the same on a mounted drive rather than building inside /home/user ? I always have the git directories inside my home folder and never have troubles.

<!-- gh-comment-id:1465241595 --> @shall0pass commented on GitHub (Mar 12, 2023): I may be ignorant here, but does building in Wsl work the same on a mounted drive rather than building inside /home/user ? I always have the git directories inside my home folder and never have troubles.
GiteaMirror commented 2026-04-14 17:16:46 -05:00
Author
Owner
Copy Link

@shahzadali84 commented on GitHub (Mar 12, 2023):

You may have to do chmod +x packages/desktop-client/bin/watch-browser. My guess is that when you first cloned the repo the execute permissions weren’t set up properly by Git.

will give it a try thanks

<!-- gh-comment-id:1465295603 --> @shahzadali84 commented on GitHub (Mar 12, 2023): > You may have to do `chmod +x packages/desktop-client/bin/watch-browser`. My guess is that when you first cloned the repo the execute permissions weren’t set up properly by Git. will give it a try thanks
GiteaMirror commented 2026-04-14 17:16:47 -05:00
Author
Owner
Copy Link

@shahzadali84 commented on GitHub (Mar 12, 2023):

I may be ignorant here, but does building in Wsl work the same on a mounted drive rather than building inside /home/user ? I always have the git directories inside my home folder and never have troubles.

will give it a try thanks

<!-- gh-comment-id:1465295627 --> @shahzadali84 commented on GitHub (Mar 12, 2023): > I may be ignorant here, but does building in Wsl work the same on a mounted drive rather than building inside /home/user ? I always have the git directories inside my home folder and never have troubles. will give it a try thanks
GiteaMirror commented 2026-04-14 17:16:47 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 1, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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=is%3Aissue+label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:1530115092 --> @github-actions[bot] commented on GitHub (May 1, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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=is%3Aissue+label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc Don’t forget to upvote the top comment with 👍!
GiteaMirror commented 2026-04-14 17:16:48 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Nov 11, 2023):

Being worked on in #1791

<!-- gh-comment-id:1806908328 --> @youngcw commented on GitHub (Nov 11, 2023): Being worked on in #1791
GiteaMirror commented 2026-04-14 17:16:49 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 8, 2024):

Custom Reports are nearly complete. If you have any new comments use #1918

<!-- gh-comment-id:1934524587 --> @youngcw commented on GitHub (Feb 8, 2024): Custom Reports are nearly complete. If you have any new comments use #1918
GiteaMirror commented 2026-04-14 17:16:49 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jul 4, 2024):

Custom reports have been officially released in v24.7.0. Thanks to everyone that contributed!

<!-- gh-comment-id:2209508381 --> @MatissJanis commented on GitHub (Jul 4, 2024): Custom reports have been officially released in v24.7.0. Thanks to everyone that contributed!
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 reports
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#14527
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?