[Feature] Add end date to repeated Schedules #584

Closed
opened 2026-02-28 19:10:26 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @gravelfreeman on GitHub (Aug 23, 2023).

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?

In this screen I searched a long time and figured out it was probably a missing feature.

We can set when the schedule starts but we can't end it by choosing a date.

image

For example; I had to set 23x scheduled entries for all the individual payments for my appliances, which are monthly payments.

Describe your ideal solution to this problem

Add a date field and date picker to be able to select an ending date. Once the end date is reached the schedule would be moved under "Show completed schedules".

Teaching and learning

No response

Originally created by @gravelfreeman on GitHub (Aug 23, 2023). ### 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? In this screen I searched a long time and figured out it was probably a missing feature. We can set when the schedule starts but we can't end it by choosing a date. ![image](https://github.com/actualbudget/actual/assets/44218371/79b95cdf-59a0-4233-b09f-12cca9512b05) For example; I had to set 23x scheduled entries for all the individual payments for my appliances, which are monthly payments. ### Describe your ideal solution to this problem Add a date field and date picker to be able to select an ending date. Once the end date is reached the schedule would be moved under "Show completed schedules". ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-02-28 19:10:26 -06:00
Author
Owner

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

@github-actions[bot] commented on GitHub (Aug 23, 2023): :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 -->
Author
Owner

@Rick-Thomas commented on GitHub (Dec 7, 2023):

Can this feature request, which has 7 votes be the same as the [#506] which has 12? I have the sensation they are both addressing the same problem of setting and end to scheduled transactions...

@Rick-Thomas commented on GitHub (Dec 7, 2023): Can this feature request, which has 7 votes be the same as the [#506] which has 12? I have the sensation they are both addressing the same problem of setting and end to scheduled transactions...
Author
Owner

@jfdoming commented on GitHub (Dec 8, 2023):

Can this feature request, which has 7 votes be the same as the [#506] which has 12? I have the sensation they are both addressing the same problem of setting and end to scheduled transactions...

Yes, I believe both will be resolved from the above PR! Hoping to get this merged soon.

@jfdoming commented on GitHub (Dec 8, 2023): > Can this feature request, which has 7 votes be the same as the [#506] which has 12? I have the sensation they are both addressing the same problem of setting and end to scheduled transactions... Yes, I believe both will be resolved from the above PR! Hoping to get this merged soon.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 14, 2023):

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

@github-actions[bot] commented on GitHub (Dec 14, 2023): :tada: This feature has been implemented in #1899 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-comment -->
Author
Owner

@Rick-Thomas commented on GitHub (Dec 14, 2023):

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

Bravoooo!!! Fantastic news!!!! Thanks and congratulations...

@Rick-Thomas commented on GitHub (Dec 14, 2023): > 🎉 This feature has been implemented in #1899 and will be released in the next version. Thanks for sharing your idea! 🎉 Bravoooo!!! Fantastic news!!!! Thanks and congratulations...
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#584