[Feature] Set finish condition to repeating transactions #178

Closed
opened 2026-02-28 18:51:13 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @rich-howell on GitHub (Jan 22, 2023).

Discussed in https://github.com/actualbudget/actual/discussions/276

Originally posted by arguser March 11, 2022

Description

Have the option to set the amount of cycles (repeats) for a repeating transaction.

Use Case

On many countries it's common to pay the full price of a product distributed in a fixed amount of months, 3, 6, 9, 12. As a user when making such transaction would be helpful to establish the end of the repeating input, so you wouldn't have to remember to remove a transaction once the period has ended.

Solution

How I imagine this being implemented:

  1. Input a transaction (spend) of let's say $100
  2. Mark transaction as repeating
  3. Set it to Monthly
  4. Set it to 3 Cycles to record only transaction and repeat it on the following two months.
  5. Once 3 iterations of the transaction occur, stop scheduling it.
Originally created by @rich-howell on GitHub (Jan 22, 2023). ### Discussed in https://github.com/actualbudget/actual/discussions/276 <div type='discussions-op-text'> <sup>Originally posted by **arguser** March 11, 2022</sup> ## Description Have the option to set the amount of cycles (repeats) for a repeating transaction. ## Use Case On many countries it's common to pay the full price of a product distributed in a fixed amount of months, 3, 6, 9, 12. As a user when making such transaction would be helpful to establish the end of the repeating input, so you wouldn't have to remember to remove a transaction once the period has ended. ## Solution How I imagine this being implemented: 1. Input a transaction (spend) of let's say $100 2. Mark transaction as repeating 3. Set it to Monthly 4. Set it to 3 Cycles to record only transaction and repeat it on the following two months. 5. Once 3 iterations of the transaction occur, stop scheduling it.</div>
GiteaMirror added the featureschedules labels 2026-02-28 18:51:13 -06:00
Author
Owner

@MatissJanis commented on GitHub (Jan 29, 2023):

Duplicate of: https://github.com/actualbudget/actual/issues/308

@MatissJanis commented on GitHub (Jan 29, 2023): Duplicate of: https://github.com/actualbudget/actual/issues/308
Author
Owner

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

Those seem to be different — this one is about stoping a schedule automatically while #308 is about changing the interval it which a schedule repeats.

@j-f1 commented on GitHub (Jan 29, 2023): Those seem to be different — this one is about stoping a schedule automatically while #308 is about changing the interval it which a schedule repeats.
Author
Owner

@MatissJanis commented on GitHub (Jan 29, 2023):

My bad, linked the wrong thing.

Here's the PR with ongoing work to make "stop transaction scheduling after X transactions" work: https://github.com/actualbudget/actual/pull/407

@MatissJanis commented on GitHub (Jan 29, 2023): My bad, linked the wrong thing. Here's the PR with ongoing work to make "stop transaction scheduling after X transactions" work: https://github.com/actualbudget/actual/pull/407
Author
Owner

@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 👍!

@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=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍!
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 -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#178