<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Setting &quot;Delay until&quot; on task with subtasks</title> 
  <pubDate>Fri, 10 Apr 2026 16:54:37 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/13737</link> 
  <atom:link rel="self" type="application/rss+xml" title="Setting &quot;Delay until&quot; on task with subtasks" href="https://bugs.horde.org/ticket/13737/rss" /> 
  <description>Setting &quot;Delay until&quot; on task with subtasks</description> 
 
   
   
  <item> 
   <title>When a task with subtasks is given a start date via &quot;Delay S</title> 
   <description>When a task with subtasks is given a start date via &quot;Delay Start Until...&quot; it is moved to the &quot;Future Tasks&quot; tab, but the subtasks stay in the &quot;Incomplete Tasks&quot; tab. In the &quot;Future Tasks&quot; tab, it is possible to tick the parent task as complete, as opposed to the &quot;Incomplete Tasks&quot; tab, where tasks with subtasks can&#039;t be marked as complete.

I think that a more consistent behavior would be to propagate the &quot;Delay Start Until&quot; setting to all child tasks.</description> 
   <pubDate>Fri, 05 Dec 2014 12:01:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13737#t86735</link> 
  </item> 
   
  <item> 
   <title>This ticket is related to 12308.

I have retested the beha</title> 
   <description>This ticket is related to 12308.

I have retested the behaviour described and I can confirm it behaves indeed differently from what is expected.
Versions used: nag 4.2.5, kronolith 4.2.9

I can even extend the given case of parent - child with another situation. The OP describes that when you set the parent task to a future start, then the parent task rightfully moves to the future tasks. And in that list the child task is not listed, and thus the list user interface does not avoid the completion tick.

But there is a more dangerous sitation:
If you keep the parent task now (no delayed start), but you delay a child task, then, in the normal task list you will only see the parent. You won&#039;t even see the child as that one has been moved to the future task tab. Again, the list no longer sees any child, and thus the parent task can be set to completed.

In general, there should be some code that is called ALWAYS when task is being completed. If that task finds any reason to refuse the completion, then it refuses it, and issues an error message indicating the reason.
</description> 
   <pubDate>Tue, 13 Oct 2015 13:41:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13737#t88830</link> 
  </item> 
   
  <item> 
   <title>See ticket #12308</title> 
   <description>See ticket #12308</description> 
   <pubDate>Fri, 22 Jan 2016 11:39:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13737#t89540</link> 
  </item> 
   
  <item> 
   <title>This was fixed by the commits for Ticket: 12308.</title> 
   <description>This was fixed by the commits for Ticket: 12308.</description> 
   <pubDate>Sat, 30 Jan 2016 18:25:20 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13737#t89763</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
