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

[GH-ISSUE #6509] [Feature] Add “Filter by: Scheduled Transactions” option #9688

New Issue
Closed
opened 2026-04-10 20:00:37 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-10 20:00:37 -05:00
Owner
Copy Link

Originally created by @Darthiss on GitHub (Dec 29, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6509

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 would like to be able to filter transactions that were created from schedules when viewing reports and account registers. This would allow me to easily include or exclude scheduled transactions for analysis and reconciliation.

Describe your ideal solution to this problem

In the filter menu, add an option to filter transactions based on whether they were created from a schedule. The option should allow users to either include only scheduled transactions or exclude scheduled transactions from the current view.

This filter should be available both in account registers and in reports, and behave consistently across both areas of the app.

Teaching and learning

To help future users understand and benefit from this feature, it should be introduced in a few complementary ways:

  • Clear labeling in the UI — The filter option should use intuitive wording such as “Scheduled transactions” with sub-options like Include / Exclude / Only. A short tooltip or helper text (e.g., “Transactions created from schedules”) would reduce confusion.

  • Consistency across views — The same filter name and behavior should appear in both account registers and reports, so users learn it once and recognize it everywhere.

  • Release notes & documentation — The feature should be mentioned in the release changelog and the filters section of the user guide, with a short example showing when you might want to exclude scheduled transactions (e.g., reconciling past activity).

Originally created by @Darthiss on GitHub (Dec 29, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6509 ### 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? As a user, I would like to be able to **filter transactions that were created from schedules** when viewing reports and account registers. This would allow me to easily include or exclude scheduled transactions for analysis and reconciliation. ### Describe your ideal solution to this problem In the filter menu, add an option to filter transactions based on whether they were created from a schedule. The option should allow users to either include only scheduled transactions or exclude scheduled transactions from the current view. This filter should be available both in account registers and in reports, and behave consistently across both areas of the app. ### Teaching and learning To help future users understand and benefit from this feature, it should be introduced in a few complementary ways: - Clear labeling in the UI — The filter option should use intuitive wording such as “Scheduled transactions” with sub-options like Include / Exclude / Only. A short tooltip or helper text (e.g., “Transactions created from schedules”) would reduce confusion. - Consistency across views — The same filter name and behavior should appear in both account registers and reports, so users learn it once and recognize it everywhere. - Release notes & documentation — The feature should be mentioned in the release changelog and the filters section of the user guide, with a short example showing when you might want to exclude scheduled transactions (e.g., reconciling past activity).
GiteaMirror added the needs votesfeature labels 2026-04-10 20:00:37 -05:00
GiteaMirror commented 2026-04-10 20:00:39 -05:00
Author
Owner
Copy Link

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

<!-- gh-comment-id:3696519015 --> @github-actions[bot] commented on GitHub (Dec 29, 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-04-10 20:00:39 -05:00
Author
Owner
Copy Link

@db-src commented on GitHub (Jan 2, 2026):

Clear labeling in the UI — The filter option should use intuitive wording such as “Scheduled transactions” with sub-options like Include / Exclude / Only. A short tooltip or helper text (e.g., “Transactions created from schedules”) would reduce confusion.

Imho it'd be better to be consistent with the existing Cleared and Reconciled fields, whose filters are "is true" and "is false". This one could be "Posted from schedule" or something, then "is true" or "false" again.

<!-- gh-comment-id:3706190209 --> @db-src commented on GitHub (Jan 2, 2026): > Clear labeling in the UI — The filter option should use intuitive wording such as “Scheduled transactions” with sub-options like Include / Exclude / Only. A short tooltip or helper text (e.g., “Transactions created from schedules”) would reduce confusion. Imho it'd be better to be consistent with the existing Cleared and Reconciled fields, whose filters are "is true" and "is false". This one could be "Posted from schedule" or something, then "is true" or "false" again.
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#9688
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?