From: Marcel van der Boom <email@example.com>
Subject: Subtasks are blocked in todo-items of ordered projects. Bug?
Date: Mon, 20 Jun 2011 15:50:11 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
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
** 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
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
My expectation of the ordered property would be that it only acted
one-level deep, regarded from a 'block-or-not' standpoint.
Marcel van der Boom -- http://hsdev.com/mvdb.vcf
HS-Development BV -- http://www.hsdev.com
We use bitcoin! -- http://bitcoin.org
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5618 bytes --]
next reply other threads:[~2011-06-20 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 13:50 Marcel van der Boom [this message]
2011-06-20 23:37 ` Subtasks are blocked in todo-items of ordered projects. Bug? Bernt Hansen
2011-06-21 8:59 ` Marcel van der Boom
2011-06-21 11:15 ` Memnon Anon
2011-06-21 11:30 ` Bernt Hansen
2011-06-21 11:40 ` Marcel van der Boom
2011-06-21 11:54 ` Carsten Dominik
2011-06-21 12:22 ` Carsten Dominik
2011-06-21 13:48 ` [PATCH] " Marcel van der Boom
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).