github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 20:23:07 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #6065] add prompt to convert future transactions to single time schedules #6305

New Issue
Closed
opened 2026-02-28 21:26:26 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:26:26 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/actualbudget/actual/pull/6065

State: closed
Merged: Yes

We often recommend against future dated transactions and tell people to use schedules instead, but there can be a bit of friction when swapping pages to add all of the fields, adding an action for the note etc. This solution has been suggested a couple of times in Discord then recently brought up again in https://github.com/actualbudget/actual/issues/6062#issuecomment-3482604852

I got videos to show all of the combinations:

  1. Adding new transaction, and shows prompt if upcoming window not long enough

https://github.com/user-attachments/assets/083ba9b0-d60f-436e-971d-9ed20169a9b1

  1. Adding a transaction with splits

https://github.com/user-attachments/assets/ceea4032-c6a8-4488-a58d-aad7d5e6b047

  1. Updating an existing transaction, split and none, showing schedule config and without upcoming window warning

https://github.com/user-attachments/assets/d8d733e9-09fa-49d2-b581-e0e25f0fbe3e

Addresses part of https://github.com/actualbudget/actual/issues/5492
Mentioned in https://github.com/actualbudget/actual/issues/1675#issuecomment-1834660848 & https://github.com/actualbudget/actual/issues/6062#issuecomment-3482604852
Closes https://github.com/actualbudget/actual/issues/5077

I also added this to mobile, and the only consideration there is that you can't delete a schedule if it's been created. I went down the consistency route and hopefully we'll get a schedules page on mobile soon, even if it is just basic view/delete page.

**Original Pull Request:** https://github.com/actualbudget/actual/pull/6065 **State:** closed **Merged:** Yes --- We often recommend against future dated transactions and tell people to use schedules instead, but there can be a bit of friction when swapping pages to add all of the fields, adding an action for the note etc. This solution has been suggested a couple of times in Discord then recently brought up again in https://github.com/actualbudget/actual/issues/6062#issuecomment-3482604852 I got videos to show all of the combinations: 1. Adding new transaction, and shows prompt if upcoming window not long enough https://github.com/user-attachments/assets/083ba9b0-d60f-436e-971d-9ed20169a9b1 2. Adding a transaction with splits https://github.com/user-attachments/assets/ceea4032-c6a8-4488-a58d-aad7d5e6b047 3. Updating an existing transaction, split and none, showing schedule config and without upcoming window warning https://github.com/user-attachments/assets/d8d733e9-09fa-49d2-b581-e0e25f0fbe3e Addresses part of https://github.com/actualbudget/actual/issues/5492 Mentioned in https://github.com/actualbudget/actual/issues/1675#issuecomment-1834660848 & https://github.com/actualbudget/actual/issues/6062#issuecomment-3482604852 Closes https://github.com/actualbudget/actual/issues/5077 I also added this to mobile, and the only consideration there is that you can't delete a schedule if it's been created. I went down the consistency route and hopefully we'll get a schedules page on mobile soon, even if it is just basic view/delete page.
GiteaMirror added the pull-request label 2026-02-28 21:26:26 -06:00
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 pull-request
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#6305
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?