Project

General

Profile

Actions

task #9

closed

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

Added by admin about 6 years ago. Updated over 1 year ago.

Status:
closed
Priority:
feature
Assignee:
Target version:
Redmine version:
unspecified

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.

Actions #1

Updated by admin about 6 years ago

  • Assignee changed from admin to cryptogopher
Actions #2

Updated by cryptogopher almost 6 years ago

  • Description updated (diff)
Actions #3

Updated by cryptogopher almost 6 years ago

  • Description updated (diff)
Actions #4

Updated by cryptogopher over 5 years ago

  • Description updated (diff)
Actions #5

Updated by cryptogopher over 5 years ago

  • Status changed from new to in progress
Actions #6

Updated by cryptogopher over 5 years ago

  • Status changed from in progress to closed

Merged in 8806497d

Actions #7

Updated by admin over 1 year ago

  • Priority changed from support to feature
Actions #8

Updated by admin over 1 year ago

  • Tracker changed from 2 to task
  • Target version set to unspecified
  • Redmine version set to unspecified
Actions

Also available in: Atom PDF