github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 19:52:56 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Frequency modifier for up to targets #1532

New Issue
Closed
opened 2026-02-28 19:46:31 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-02-28 19:46:31 -06:00
Owner
Copy Link

Originally created by @ColinHebert on GitHub (Oct 22, 2024).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

I am trying to replicate a behaviour of YNAB that allows doing a refill budget by $x weekly.

This would, for example, allow you to set a budget for, say, "eating out" over a month based on the number of weeks and re-fill the budget based on the number of weeks in the month.

Describe your ideal solution to this problem

Currently up to is only working "monthly" (implied), I'm wondering whether it'd be possible to have an explicit frequency set:

  • #template up to $3 daily - which would be the equivalent to #template up to $84 in February or #template up to $93 in August
  • #template up to $50 weekly - which would be the equivalent to #template up to $200 in a month with 4 weeks or #template up to $250 in a month with 5 weeks
  • #template up to $100 [monthly] - which is the current behaviour in Actual

In terms of implementation, I'm not sure it'd make sense to have frequency for longer periods of time than monthly.

Teaching and learning

No response

Originally created by @ColinHebert on GitHub (Oct 22, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I am trying to replicate a behaviour of YNAB that allows doing a `refill budget by $x weekly`. This would, for example, allow you to set a budget for, say, "eating out" over a month based on the number of weeks and re-fill the budget based on the number of weeks in the month. ### Describe your ideal solution to this problem Currently `up to` is only working "monthly" (implied), I'm wondering whether it'd be possible to have an explicit frequency set: - `#template up to $3 daily` - which would be the equivalent to `#template up to $84` in February or `#template up to $93` in August - `#template up to $50 weekly` - which would be the equivalent to `#template up to $200` in a month with 4 weeks or `#template up to $250` in a month with 5 weeks - `#template up to $100 [monthly]` - which is the current behaviour in Actual In terms of implementation, I'm not sure it'd make sense to have frequency for longer periods of time than monthly. ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-02-28 19:46:31 -06:00
GiteaMirror commented 2026-02-28 19:46:32 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 22, 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 👍!

@github-actions[bot] commented on GitHub (Oct 22, 2024): :sparkles: Thanks for sharing your idea! :sparkles: 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-02-28 19:46:32 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 22, 2024):

How would you suggest determining if there are 5 weeks or just 4 in a month? The other templates count weeks from a starting day.

@youngcw commented on GitHub (Oct 22, 2024): How would you suggest determining if there are 5 weeks or just 4 in a month? The other templates count weeks from a starting day.
GiteaMirror commented 2026-02-28 19:46:33 -06:00
Author
Owner
Copy Link

@ColinHebert commented on GitHub (Oct 22, 2024):

That's a really good point.

Maybe the wording should be weekly on Monday, which would allow us to count the number of Mondays in the month.

I'm not sure what a sensible default would be if we wanted just weekly, it could either be the weekday of the first day of the month (I don't know if this would have any strong side effects) or a default to Sunday (I'm not American, but ultimately, when we count the number of weeks, Sunday is just as good as any other day). Alternatively no sensible default could work as well but I think it's a worse option.

Edit: Thinking it through, the suggestion of "first day of the month" is really bad as it means the budget would be potentially set on two days of the same weeks (end of one month beginning of the other), so I guess picking a default day when not specified is as good as anything.

@ColinHebert commented on GitHub (Oct 22, 2024): That's a really good point. Maybe the wording should be `weekly on Monday`, which would allow us to count the number of Mondays in the month. I'm not sure what a sensible default would be if we wanted just `weekly`, ~~it could either be the weekday of the first day of the month (I don't know if this would have any strong side effects) or~~ a default to Sunday (I'm not American, but ultimately, when we count the number of weeks, Sunday is just as good as any other day). Alternatively no sensible default could work as well but I think it's a worse option. --- Edit: Thinking it through, the suggestion of "first day of the month" is really bad as it means the budget would be potentially set on two days of the same weeks (end of one month beginning of the other), so I guess picking a default day when not specified is as good as anything.
GiteaMirror commented 2026-02-28 19:46:33 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 23, 2024):

@ColinHebert Can you try #3714 and see if it is everything you hoped for?

@youngcw commented on GitHub (Oct 23, 2024): @ColinHebert Can you try #3714 and see if it is everything you hoped for?
GiteaMirror commented 2026-02-28 19:46:33 -06:00
Author
Owner
Copy Link

@Teprifer commented on GitHub (Oct 23, 2024):

I like weekly on Monday type as it allows for weeklies that are on different days.

@Teprifer commented on GitHub (Oct 23, 2024): I like `weekly on Monday` type as it allows for weeklies that are on different days.
GiteaMirror commented 2026-02-28 19:46:34 -06:00
Author
Owner
Copy Link

@ColinHebert commented on GitHub (Oct 24, 2024):

Tested and it indeed fixes this. Nicely done @youngcw !

@ColinHebert commented on GitHub (Oct 24, 2024): Tested and it indeed fixes this. Nicely done @youngcw !
GiteaMirror commented 2026-02-28 19:46:34 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 4, 2024):

🎉 This feature has been implemented in #3754 and will be released in the next version. Thanks for sharing your idea! 🎉

@github-actions[bot] commented on GitHub (Nov 4, 2024): :tada: This feature has been implemented in #3754 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-comment -->
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 feature
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#1532
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?