github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-10 23:54:00 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[Feature] Report end date should go up to latest transaction date instead of current date #2269

New Issue
Closed
opened 2026-02-28 20:08:33 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 20:08:33 -06:00
Owner
Copy Link

Originally created by @csenel on GitHub (Jul 9, 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?

As a user, I add future transactions to my accounts to see what the next 6-12 months look like. I would like to see how Net Worth or Cash Flow reports will look like in the future too.

However, currently there is a limitation where you can only select up to current date in Reports.

Describe your ideal solution to this problem

Instead of limiting the end date to current date, the date selector should be up to the latest date from transactions. (similar to how start date range is fetched.)

Teaching and learning

No response

Originally created by @csenel on GitHub (Jul 9, 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? As a user, I add future transactions to my accounts to see what the next 6-12 months look like. I would like to see how Net Worth or Cash Flow reports will look like in the future too. However, currently there is a limitation where you can only select up to current date in Reports. ### Describe your ideal solution to this problem Instead of limiting the end date to current date, the date selector should be up to the latest date from transactions. (similar to how start date range is fetched.) ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-02-28 20:08:33 -06:00
GiteaMirror commented 2026-02-28 20:08:35 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 9, 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 (Jul 9, 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:08:35 -06:00
Author
Owner
Copy Link

@teemue commented on GitHub (Jul 16, 2025):

Please implement this!

@teemue commented on GitHub (Jul 16, 2025): Please implement this!
GiteaMirror commented 2026-02-28 20:08:35 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 21, 2025):

🎉 This feature has been implemented in #5753 and will be released in the next version. Thanks for sharing your idea! 🎉

@github-actions[bot] commented on GitHub (Sep 21, 2025): :tada: This feature has been implemented in #5753 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-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
tech-support
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#2269
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?