mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 11:42:54 -05:00
[Feature] Possibility to add a note to the schedule payments #191
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#191
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 @rich-howell on GitHub (Jan 22, 2023).
Discussed in https://github.com/actualbudget/actual/discussions/243
Originally posted by fstybel September 5, 2022
I would like to create multiple scheduled regular payments but I'm worried that I will forget for what purpose each of them was created. So, I would like to have the possibility to add a note (like for transactions) to each of them.
@github-actions[bot] commented on GitHub (May 1, 2023):
✨ Thanks for sharing your idea! ✨
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!
@ricketyboo commented on GitHub (Nov 30, 2023):
This seems to duplicate https://github.com/actualbudget/actual/issues/578 where some further discussion has been had including an older PR
@ricketyboo commented on GitHub (Nov 30, 2023):
@MatissJanis apologies for the direct ping especially if this isn't for you, but you seem to be the active on in the issue management from what I can see in docs and activity. There's a few feature requests that are all boiling down to roughly the same set of changes around making schedule entry more like transaction entry. Is there a way we can merge these into a single point so the votes aren't being scattered across multiple similar requests?
Here's a small cluster of very similar issues, probably a few more that I've missed.
@matt-fidd commented on GitHub (Jan 29, 2025):
These can be added through the rule and will display in the UI