actualbudget/actual

Scheduled transactions don't handle 29th/30th/31st dates appropriately

Open

#1,062 opened on May 25, 2023

View on GitHub
 (12 comments) (2 reactions) (0 assignees)JavaScript (603 forks)batch import
bughelp wantedschedules

Repository metrics

Stars
 (7,129 stars)
PR merge metrics
 (Avg merge 4d 15h) (165 merged PRs in 30d)

Description

Running v23.5.0, when I set up a monthly scheduled transaction starting 31/5 the current behaviour is to not schedule anything for June, because there is no 31st day in June. image I'm sure opinions will differ on whether the best option would be to schedule the transaction for 30/6 or for 1/7, I don't have an opinion on that as long as it gets scheduled somewhere. 🙂

Contributor guide

Research direction
Investigate the scheduled transaction logic for handling month end dates. Look for code that calculates the next occurrence and see how it handles months with fewer days. Consider using last day of month or next month's first day as fallback.
Tech stack
javascript
Domain
backendfrontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65