github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #578] [Feature] Allow customizing “notes” field directly from schedules #49362

New Issue
Closed
opened 2026-04-30 10:41:52 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-30 10:41:52 -05:00
Owner
Copy Link

Originally created by @j-f1 on GitHub (Jan 26, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/578

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?

When I have multiple recurring transactions paid out to a single payee (for example, I have several subscriptions to different apps through the App Store, but the payee for all of those payments ends up being Apple), it is confusing to look at the schedule list because I can’t easily differentiate between the different schedules except by trying to remember their pricing.

Describe your ideal solution to this problem

  • Add a new field to the schedules editor called “Name” or “Notes” that allows entering a custom name for a schedule
  • This value would be automatically entered into the “notes” field of any matched transactions (probably using the standard “set note to” action on the underlying rule)
  • The schedule list would gain a new column that shows this field for disambiguation purposes

Teaching and learning

I think people would naturally notice the feature the next time they create a new schedule. They’d also be likely to notice the new column in the schedules UI if this affects them. No documentation should be needed.

Originally created by @j-f1 on GitHub (Jan 26, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/578 ### 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? When I have multiple recurring transactions paid out to a single payee (for example, I have several subscriptions to different apps through the App Store, but the payee for all of those payments ends up being Apple), it is confusing to look at the schedule list because I can’t easily differentiate between the different schedules except by trying to remember their pricing. ### Describe your ideal solution to this problem - Add a new field to the schedules editor called “Name” or “Notes” that allows entering a custom name for a schedule - This value would be automatically entered into the “notes” field of any matched transactions (probably using the standard “set note to” action on the underlying rule) - The schedule list would gain a new column that shows this field for disambiguation purposes ### Teaching and learning I think people would naturally notice the feature the next time they create a new schedule. They’d also be likely to notice the new column in the schedules UI if this affects them. No documentation should be needed.
GiteaMirror added the feature label 2026-04-30 10:41:52 -05:00
GiteaMirror commented 2026-04-30 10:41:54 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jan 26, 2023):

Check out my initial attempts at #268. The code isn’t likely to be worth using, but someone working on this feature might find my learnings there valuable.

<!-- gh-comment-id:1405774732 --> @j-f1 commented on GitHub (Jan 26, 2023): Check out my initial attempts at #268. The code isn’t likely to be worth using, but someone working on this feature might find my learnings there valuable.
GiteaMirror commented 2026-04-30 10:41:55 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Jan 26, 2023):

This issue has been a problem in a number of Finance Apps that I tried. In the absence of a solution, such as is proposed here,I developed a work around that has "stuck" for me. I include the extra description in the Payee name. So:
Apple (iCloud)
Apple (Music)
Apple (1Password)
And so on.

Just commenting in case this helps anyone in the interim.

<!-- gh-comment-id:1405780001 --> @Kidglove57 commented on GitHub (Jan 26, 2023): This issue has been a problem in a number of Finance Apps that I tried. In the absence of a solution, such as is proposed here,I developed a work around that has "stuck" for me. I include the extra description in the Payee name. So: Apple (iCloud) Apple (Music) Apple (1Password) And so on. Just commenting in case this helps anyone in the interim.
GiteaMirror commented 2026-04-30 10:41:56 -05:00
Author
Owner
Copy Link

@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=is%3Aissue+label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:1530116379 --> @github-actions[bot] commented on GitHub (May 1, 2023): :sparkles: Thanks for sharing your idea! :sparkles: 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=is%3Aissue+label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc Don’t forget to upvote the top comment with 👍!
GiteaMirror commented 2026-04-30 10:41:57 -05:00
Author
Owner
Copy Link

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

duplicate of #519

<!-- gh-comment-id:2423000141 --> @youngcw commented on GitHub (Oct 18, 2024): duplicate of #519
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
tech-support
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#49362
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?