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

[PR #3310] [MERGED] Add option to set how far out the upcoming scheduled transactions are shown in the account view. #34986

New Issue
Closed
opened 2026-04-20 22:03:02 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 22:03:02 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/3310
Author: @SamBobBarnes
Created: 8/24/2024
Status: ✅ Merged
Merged: 10/11/2024
Merged by: @youngcw

Base: master ← Head: Custom-upcoming-scheduled-transaction-window

📝 Commits (10+)

📊 Changes

25 files changed (+459 additions, -276 deletions)

View changed files

📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-checks-the-page-visuals-1-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-checks-the-page-visuals-2-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-checks-the-page-visuals-3-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-1-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-10-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-11-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-12-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-2-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-3-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-4-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-5-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-6-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-7-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-8-chromium-linux.png (+0 -0)
📝 packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-9-chromium-linux.png (+0 -0)
📝 packages/desktop-client/src/components/schedules/index.tsx (+11 -1)
➕ packages/desktop-client/src/components/settings/Upcoming.tsx (+85 -0)
📝 packages/desktop-client/src/components/settings/index.tsx (+1 -1)
📝 packages/loot-core/src/client/data-hooks/schedules.tsx (+14 -10)
📝 packages/loot-core/src/server/prefs.ts (+9 -0)

...and 5 more files

📄 Description

Add option to set how far out the upcoming scheduled transactions are shown in the account view.
This option can be set to 1, 7, 14, or 30 days out from today.

The only thing lacking from this enhancement, that I couldn't work out how to implement, was longer periods (eg 2-3 mo) because I couldn't work out how to show more than just the next instance of a scheduled transaction. This may also be an issue if a user has scheduled transactions that should occur more than once per visible period.

I implemented this enhancement because I was frustrated that I could only see 7 days into the future and could not plan ahead very far into the future. This is something that I wanted because I was moving from quicken where I utilized seeing a month in the future often for planning purposes.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/3310 **Author:** [@SamBobBarnes](https://github.com/SamBobBarnes) **Created:** 8/24/2024 **Status:** ✅ Merged **Merged:** 10/11/2024 **Merged by:** [@youngcw](https://github.com/youngcw) **Base:** `master` ← **Head:** `Custom-upcoming-scheduled-transaction-window` --- ### 📝 Commits (10+) - [`d56622d`](https://github.com/actualbudget/actual/commit/d56622ddd2dc123742ea84661746de84cb8c0285) initial poking around - [`4b78518`](https://github.com/actualbudget/actual/commit/4b7851849df0c4bf1cf7a0041537ca0ed9440994) ui changes and setting - [`27c7889`](https://github.com/actualbudget/actual/commit/27c788968a64116c99e9429c76e4e763cf104304) wip - [`2b34e3b`](https://github.com/actualbudget/actual/commit/2b34e3befc669c03d27c129d4cfefc47c7fcb2d9) null check - [`2486cdd`](https://github.com/actualbudget/actual/commit/2486cdd36fa1428e3a41098cfd03a4190425cfc6) removed more than a month - [`f7ff09d`](https://github.com/actualbudget/actual/commit/f7ff09d267d4eb2aa1a574782c7ef46f96c395d9) prettier - [`6300404`](https://github.com/actualbudget/actual/commit/63004048b914fcba9c366803debb300629f1a3a8) todo - [`558422a`](https://github.com/actualbudget/actual/commit/558422aef793ff4e745fdc709ff251865ae2eb0d) get status tests - [`4460f7d`](https://github.com/actualbudget/actual/commit/4460f7d92950765791f9d927cd2788e0dd3c231c) added prefs to app.ts - [`2246966`](https://github.com/actualbudget/actual/commit/22469661f64be518c24caea53d5af93be00b8829) updated to use LocalPrefs bc of limitation of app.ts ### 📊 Changes **25 files changed** (+459 additions, -276 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-checks-the-page-visuals-1-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-checks-the-page-visuals-2-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-checks-the-page-visuals-3-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-1-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-10-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-11-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-12-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-2-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-3-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-4-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-5-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-6-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-7-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-8-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/e2e/schedules.test.js-snapshots/Schedules-creates-a-new-schedule-posts-the-transaction-and-later-completes-it-9-chromium-linux.png` (+0 -0) 📝 `packages/desktop-client/src/components/schedules/index.tsx` (+11 -1) ➕ `packages/desktop-client/src/components/settings/Upcoming.tsx` (+85 -0) 📝 `packages/desktop-client/src/components/settings/index.tsx` (+1 -1) 📝 `packages/loot-core/src/client/data-hooks/schedules.tsx` (+14 -10) 📝 `packages/loot-core/src/server/prefs.ts` (+9 -0) _...and 5 more files_ </details> ### 📄 Description Add option to set how far out the upcoming scheduled transactions are shown in the account view. This option can be set to 1, 7, 14, or 30 days out from today. The only thing lacking from this enhancement, that I couldn't work out how to implement, was longer periods (eg 2-3 mo) because I couldn't work out how to show more than just the next instance of a scheduled transaction. This may also be an issue if a user has scheduled transactions that should occur more than once per visible period. I implemented this enhancement because I was frustrated that I could only see 7 days into the future and could not plan ahead very far into the future. This is something that I wanted because I was moving from quicken where I utilized seeing a month in the future often for planning purposes. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-20 22:03:02 -05: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#34986
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?