Patch #3195

issue's start date could be the latest due date of predecessors

Added by Sanghyuk Suh over 8 years ago. Updated over 2 years ago.

Status:NewStart date:2009-04-17
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:Candidate for next minor release

Description

currently, the start date of a issue must be later than the latest due date of predecessors.
it means i cannot continue working in the same day.

i have made a patch for fix it.

successor_soonest_start.diff Magnifier (521 Bytes) Sanghyuk Suh, 2009-04-17 06:54


Related issues

Duplicated by Redmine - Defect #19516: Issue "preceeds" error: If B follows A, B starting date !... Closed

History

#1 Updated by Yohann Monnier over 8 years ago

I had the same problem. Thank you for this improvment. I hope it will be published in the main trunk.

#2 Updated by Anonymous about 8 years ago

+1

#3 Updated by Etienne Massip over 6 years ago

  • Category set to Issues
  • Target version set to Candidate for next minor release

#4 Updated by Maxim Nikolaevich about 6 years ago

i disagree
I can continue work on another task in same day

#5 Updated by Mischa The Evil about 6 years ago

Maxim Nikolaevich wrote:

i disagree

I can continue work on another task in same day

Looking at your second sentence, you agree (instead of disagree) with a change as proposed in this issue...

#6 Updated by Go MAEDA over 2 years ago

  • Duplicated by Defect #19516: Issue "preceeds" error: If B follows A, B starting date !=< ending date of A, should be Bs !< Ae added

#7 Updated by Go MAEDA over 2 years ago

+1
I think this should be changed.
When I have finished the preceding task, I will start following tasks in the same day.

#8 Updated by David Gessel over 2 years ago

I apologize, I didn't find this 6 year old Issue and filed #19516. Thanks to Go MAEDA for catching it.

If B's start (Bs) follows A's end (Ae), Bs !=< Ae does not reflect typical reality, it should be Bs !< Ae.

It is perfectly logical and reasonable to plan to start issue B the same day issue A is resolved. There's no reason to enforce in planning an "A's done! Everybody go home early!" rule. It should be entirely practical to plan to resolve 100 sequential issues on a single day, though perhaps a bit optimistic even just for the overhead of closing them out.

Also available in: Atom PDF