Feature #298
Configurable recurring task count
| Status: | Closed | Start: | 10/06/2009 | |
| Priority: | Normal | Due date: | ||
| To: | Paul Beckingham | % Done: | 100% |
|
| Category: | core | Spent time: | 1.00 hour | |
| Target version: | 1.9.2 - Kuwagata | Estimated time: | 1.00 hour | |
Description
When a recurring task is created, instances of that task are generated for each recurring date between the due date and the next non-overdue date. That means there is at most, one recurring task in the future.
This works well for command line reports, but does not work well for including tasks on a calendar. For example, monthly recurring tasks need to be generated for the entire year, if a yearly calendar is to be created.
History
Updated by David Patrick 338 days ago
An alternative would be to allow an end-date for the repeating actions, to be specified for reports or exports.
Updated by Paul Beckingham 297 days ago
- Category set to core
- Status changed from New to Assigned
- To set to Paul Beckingham
- Target version set to 2.1.x - Wakizashi
Updated by Federico Hernandez 102 days ago
- Target version changed from 2.1.x - Wakizashi to 1.9.2 - Kuwagata
Updated by Paul Beckingham 88 days ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
- Estimated time set to 1.00
The new 'recurrence.limit' (default 1) will control how many future recurring tasks are generated.