Project

General

Profile

feature #9

New scheduling algorithm: fixed schedule, but recur only after closing last issue

Added by admin 9 months ago. Updated 4 days ago.

Status:
closed
Priority:
normal
Assignee:

Description

Next recurrence should be added after close date (i.e. recurrences scheduled between last issue and close date should be omitted/not created). This should work with in-place modification.

This is meant for tasks that should be completed on fixed schedule, but can be omitted if previous planned execution is delayed till the next one. In this scenario we don't want to have multiple recurrences open at the same time (when multiple executions can be merged into one, e.g. downloading all past bank account statements).

Description for 'based on' form field: last recurrence date, but only after close date
Should allow for multiple in-place schedules, but only of the same algorithm.


Token votes

History

#1 Updated by admin 9 months ago

  • Assignee changed from admin to cryptogopher

#2 Updated by cryptogopher 5 months ago

  • Description updated (diff)

#3 Updated by cryptogopher 5 months ago

  • Description updated (diff)

#4 Updated by cryptogopher 2 months ago

  • Description updated (diff)

#5 Updated by cryptogopher 15 days ago

  • Status changed from new to in progress

#6 Updated by cryptogopher 4 days ago

  • Status changed from in progress to closed

Merged in 8806497d

Also available in: Atom PDF