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

[PR #6559] [MERGED] Update category schedule indicator to honor the upcoming days length setting #55905

New Issue
Closed
opened 2026-05-01 03:17:12 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-01 03:17:12 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/6559
Author: @joel-jeremy
Created: 1/5/2026
Status: ✅ Merged
Merged: 1/16/2026
Merged by: @joel-jeremy

Base: master ← Head: category-schedule-indicator-upcoming-days

📝 Commits (3)

  • 3f4311f Update category schedule indicator to honor the upcoming days length setting
  • 4731e8b [autofix.ci] apply automated fixes
  • 7d7cfb0 Update filter

📊 Changes

2 files changed (+24 additions, -4 deletions)

View changed files

📝 packages/desktop-client/src/hooks/useCategoryScheduleGoalTemplateIndicator.ts (+18 -4)
➕ upcoming-release-notes/6559.md (+6 -0)

📄 Description

Right now the schedule indicator on the budget page only shows on the month when a scheduled is set. So if it is scheduled on Feb 1 and today is January 31, the schedule won't show up in January's budget page giving the impression to the user that there are no upcoming schedules.

Steps to test changes:

  1. Create a Test schedule dated for next month (Feb 1, 2026)
  2. Add #template schedule Test to a category
  3. Apply the template
  4. Change the schedule upcoming length setting to 1 month

The schedule indicator for the category should show up in January budget page as well as in February because it is within the 1 month window

🔄 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/6559 **Author:** [@joel-jeremy](https://github.com/joel-jeremy) **Created:** 1/5/2026 **Status:** ✅ Merged **Merged:** 1/16/2026 **Merged by:** [@joel-jeremy](https://github.com/joel-jeremy) **Base:** `master` ← **Head:** `category-schedule-indicator-upcoming-days` --- ### 📝 Commits (3) - [`3f4311f`](https://github.com/actualbudget/actual/commit/3f4311ffba3ee5dab89c10099e13eca08cc19642) Update category schedule indicator to honor the upcoming days length setting - [`4731e8b`](https://github.com/actualbudget/actual/commit/4731e8bafa392bc90780c4a194a9dc951657f8b2) [autofix.ci] apply automated fixes - [`7d7cfb0`](https://github.com/actualbudget/actual/commit/7d7cfb03ed857f381b15dbd4a323a2db794ed797) Update filter ### 📊 Changes **2 files changed** (+24 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/hooks/useCategoryScheduleGoalTemplateIndicator.ts` (+18 -4) ➕ `upcoming-release-notes/6559.md` (+6 -0) </details> ### 📄 Description <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> Right now the schedule indicator on the budget page only shows on the month when a scheduled is set. So if it is scheduled on Feb 1 and today is January 31, the schedule won't show up in January's budget page giving the impression to the user that there are no upcoming schedules. Steps to test changes: 1. Create a `Test` schedule dated for next month (Feb 1, 2026) 2. Add `#template schedule Test` to a category 3. Apply the template 4. Change the schedule upcoming length setting to `1 month` The schedule indicator for the category should show up in January budget page as well as in February because it is within the 1 month window --- <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-05-01 03:17:12 -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#55905
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?