mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-11 11:59:55 -05:00
[GH-ISSUE #2498] [Feature] Better upcoming payments for ranged schedules #7941
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#7941
Reference in New Issue
Block a user
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?
Originally created by @psybers on GitHub (Mar 23, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2498
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Sometimes, recurring payments are within a range. In my example, the cost is based on the number of days that activity is offered that month, so holidays and the number of weeks make it vary.
For example, you might have a monthly payment that varies between
$-80and$-320and then set the schedule up as a range. When you set the schedule to a range, it shows upcoming transactions using the average of that range, e.g.$-160:Depending on the range, that might not be very accurate.
Describe your ideal solution to this problem
What would be more useful is to find all linked payments for that schedule, e.g.:
and then use the average of that set of transactions as the scheduled transaction's amount. In this example, that would be
$-165.68instead of the range's average of$-160. This would be very easy to calculate, and would better handle scenarios where most payments are similar and you have a few one-off payments that are very different. In the example above, the low payment of ~$90is an outlier—most payments are closer to$190.A better solution would be one that can learn from the set of transactions already linked and forecast forward based on that. This could be useful in two scenarios. The first is where the payment somewhat alternates between a couple of values. The second is when the payment is slowly increasing (or, though this rarely happens in life, decreasing) over time. Here it would be nice if it then tries to guess a better estimate than the average.
Teaching and learning
This should be fully automated, so nothing needs to happen on the user's end. The documentation might be updated to describe that behavior, though the current documentation on creating schedules does not mention the ranges at all.
@github-actions[bot] commented on GitHub (Mar 23, 2024):
✨ Thanks for sharing your idea! ✨
This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!