github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 12:28:57 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #7436] [Feature] Schedule Page Indicate if Auto-Add Transaction #28871

New Issue
Closed
opened 2026-04-18 05:36:43 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-18 05:36:43 -05:00
Owner
Copy Link

Originally created by @totallynotjon on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7436

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 looking at the overview of schedules that are setup, most details are already present: Name, Payee, Account, Amount, Next Date etc.

Missing from this is whether or not the schedule is set to automatically add the transaction. To get this information it requires clicking into each schedule to see the status of the checkbox.

This is a bit cumbersome when trying to audit a lot of schedules for this information.

Describe your ideal solution to this problem

My ideal solution would be a simple visual indicator on the summary page. This can be identical to what is setup for the "Recurring" field: another very small column which shows a check if it is set to automatically add.

The only question is what the column would be named. Maybe "Add Transaction"?

A more complex solution would be some other way to filter on the summary page for this information. If it's determined that column space is limited, and we don't want to add another column, being able to filter would also solve this problem.

Teaching and learning

The ideal solution should be so straightforward that documentation shouldn't really be needed. A column with a checkbox that represents a checkbox when managing schedules should be straight forward.

Documentation might need to be updated for how the overall page looks/screenshots etc.

Originally created by @totallynotjon on GitHub (Apr 9, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7436 ### 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? When looking at the overview of schedules that are setup, most details are already present: Name, Payee, Account, Amount, Next Date etc. Missing from this is whether or not the schedule is set to automatically add the transaction. To get this information it requires clicking into each schedule to see the status of the checkbox. This is a bit cumbersome when trying to audit a lot of schedules for this information. ### Describe your ideal solution to this problem My ideal solution would be a simple visual indicator on the summary page. This can be identical to what is setup for the "Recurring" field: another very small column which shows a check if it is set to automatically add. The only question is what the column would be named. Maybe "Add Transaction"? A more complex solution would be some other way to filter on the summary page for this information. If it's determined that column space is limited, and we don't want to add another column, being able to filter would also solve this problem. ### Teaching and learning The ideal solution should be so straightforward that documentation shouldn't really be needed. A column with a checkbox that represents a checkbox when managing schedules should be straight forward. Documentation might need to be updated for how the overall page looks/screenshots etc.
GiteaMirror added the needs votesfeature labels 2026-04-18 05:36:43 -05:00
GiteaMirror commented 2026-04-18 05:36:45 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 9, 2026):

✨ 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:4210798868 --> @github-actions[bot] commented on GitHub (Apr 9, 2026): :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 -->
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#28871
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?