Hi all,

I've run into an annoyance wrt the :ORDERED: property and the blocking
of tasks due to it.

Here is the minimal usecase:

--- 
* TODO Project like header, containing subtasks
  :PROPERTIES:
  :ORDERED:  t
  :END: 
** TODO This item is the first to be done in the project
   This one is not blocked, as I expect.
** TODO Next task with subtasks
   This is blocked by the sibling above, which is what I expect 
*** TODO Subtask of a blocked sibling.
    This seems to be blocked and I can't understand why. Marking it DONE would not mark the parent
    done (neither explicit nor implicit). Why is it blocked then? Bug?
*** TODO Second item in the blocked
    This is also blocked, which could be right, because the parent
    project has an ordered property and the sibling above is not yet
    complete. 
---

Should the first task in a subproject of a project
having the ':ORDERED:' property set to true be blocked from marking
'DONE'? If so, why?

The above minimal case is easy, but it's far from trivial to see why
tasks in projects are blocked if the project is longer and has more
outline levels.

My expectation of the ordered property would be that it only acted
one-level deep, regarded from a 'block-or-not' standpoint. 

Thoughts?

marcel


-- 
Marcel van der Boom  -- http://hsdev.com/mvdb.vcf
HS-Development BV    -- http://www.hsdev.com
We use bitcoin!      -- http://bitcoin.org