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] Add configuration option to collapse future transactions #898

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

Originally created by @tavlima on GitHub (Jan 29, 2024).

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?

It would be really useful to have an option to collapse future transactions, when viewing the account transactions. My context is basically installments purchases on credit card, which is really common in some countries (Brazil, in my case). It is really annoying to have to scroll a couple of pages just because I have 50 future installments, related to multiple purchases.

FWIW, I'm using a custom importer to create those future transactions, based on data provided by my banks.

Describe your ideal solution to this problem

I'm thinking something like what nYNAB does, where the future transactions are collapsed by default but you have the option to show them.

Teaching and learning

For those coming from nYNAB, it would be intuitive, but other could be left wondering wth their transactions are, which is why this behavior should, IMHO, be disabled by default, with a new option in the settings menu to enabled it (whether future transactions should be collapsed or not).

Originally created by @tavlima on GitHub (Jan 29, 2024). ### 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? It would be really useful to have an option to collapse future transactions, when viewing the account transactions. My context is basically installments purchases on credit card, which is really common in some countries (Brazil, in my case). It is really annoying to have to scroll a couple of pages just because I have 50 future installments, related to multiple purchases. FWIW, I'm using a custom importer to create those future transactions, based on data provided by my banks. ### Describe your ideal solution to this problem I'm thinking something like what nYNAB does, where the future transactions are collapsed by default but you have the option to show them. ### Teaching and learning For those coming from nYNAB, it would be intuitive, but other could be left wondering wth their transactions are, which is why this behavior should, IMHO, be disabled by default, with a new option in the settings menu to enabled it (whether future transactions should be collapsed or not).
GiteaMirror added the featureneeds votes labels 2026-02-28 19:24:28 -06:00
GiteaMirror commented 2026-02-28 19:24:29 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 29, 2024):

✨ 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 (Jan 29, 2024): :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#898
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?