Project

General

Profile

Actions

task #1

closed

Add separate field (anchor_to_start:bool) to specify if issue is recurred based on start or due date

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

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

Description

Currently start/due can only be specified for monthly recurrences. While it is not needed for fixed daily/weekly modes (yearly mode can make use of it on leap years), it should be possible for flexible modes to have either start or due date based on last recurrence close date (currently plugin decides which one to use, based on availability, but defaults to due date). That's why anchor date should be separated from recurrence mode.

Migration of existing records can be as follows:
  • monthly_start/due are converted accordingly,
  • all others: if start_date available and due_date empty anchor_to_start=true, false otherwise
Actions #1

Updated by cryptogopher about 6 years ago

  • Tracker changed from task to 2
  • Description updated (diff)
Actions #2

Updated by cryptogopher about 6 years ago

  • Subject changed from Add separate field to specify if issue is recurred based on start or due date to Add separate field (anchor_to_start:bool) to specify if issue is recurred based on start or due date
  • Description updated (diff)
Actions #3

Updated by cryptogopher about 6 years ago

  • Priority changed from support to bug
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 closed
Actions #6

Updated by cryptogopher over 5 years ago

  • Description updated (diff)
Actions #7

Updated by admin over 1 year ago

  • Priority changed from bug 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