mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 11:42:54 -05:00
[Feature] Optional setting a Note and/or Category when creating a Schedule or referencing to Schedule Name in Rule #761
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#761
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 @thed0g12345 on GitHub (Nov 25, 2023).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
As described here in hostile words, for which I apologize, since it was probably out of frustration Actual being so close to perfection.
The issue lies when having two (or more) scheduled payments on the same day, with same amount, payee and account - as in example transaction fees for the scheduled payment to the bank (bill).
A workaround was proposed to have a different payee for each such case. Another own workaround is lying about the transaction date and switching the schedule in Actual to a day later or earlier. Another one would be to adding the transaction fee to the amount of the scheduled payment.
All three are valid workarounds, but prove the inflexibility of the current system in this point. Lying in our transaction statements isn't something an expense tracker or budget tool should propose, specially if some are using automation APIs for reconcilliation of Accounts.
Describe your ideal solution to this problem
My proposition would be to simply allow setting a Note and/or selecting the Category when creating a Schedule. Those two fields would be optional, but additional Rules wouldn't be needed in such case. This would also follow the functionality as it was in YNAB.
Another proposition for change would be to have the possibility to add the "Schedule Name" in the Rule, so we'd add the condition "when Schedule Name is". This way we would have a specific reference in the name, the Rule could be ran and properly differentiate between both Schedules, specially since Schedules has to have unique names already.
Teaching and learning
Describing it that it works as people were used to it if coming from YNAB would be helpful to those who migrated or are looking to migrate from YNAB. I've used and trialed many expense tracker solutions in the past prior YNAB and all scheduled transactions had the proposed functionality.
@github-actions[bot] commented on GitHub (Nov 25, 2023):
✨ 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 👍!