On Jun 21, 2011, at 1:54 PM, Carsten Dominik wrote:
>
> On Jun 21, 2011, at 1:40 PM, Marcel van der Boom wrote:
>
>>
>> On di 21-jun-2011 07:30
>> Bernt Hansen wrote:
>>
>>> You can also force the task state to DONE with a triple prefix (C-u
>>> C-u C-u C-c C-t d) which will ignore the block
On Jun 21, 2011, at 1:40 PM, Marcel van der Boom wrote:
>
> On di 21-jun-2011 07:30
> Bernt Hansen wrote:
>
>> You can also force the task state to DONE with a triple prefix (C-u
>> C-u C-u C-c C-t d) which will ignore the blocking rules for this state
>> change.
And one more alternative:
If
On di 21-jun-2011 07:30
Bernt Hansen wrote:
> You can also force the task state to DONE with a triple prefix (C-u
> C-u C-u C-c C-t d) which will ignore the blocking rules for this state
> change.
I think I'll use this, sounds the simplest for my usecase.
Thanks,
marcel
--
Marcel van der Boo
Marcel van der Boom writes:
> On ma 20-jun-2011 19:37
> Bernt Hansen wrote:
>
>>> 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?
>>
>> I think the answer is yes it should be blocked because the
Marcel van der Boom writes:
[...]
> That will allow me to work on the subitems in parallel. Obvious
> disadvantage is that the subproject as such can only have a
> 'count' or 'percentage' but not a 'state' and thus cannot be tracked
> anymore.
>
> Any other suggestions for a way to work on subit
On ma 20-jun-2011 19:37
Bernt Hansen wrote:
>> 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?
>
> I think the answer is yes it should be blocked because the entire tree
> is blocked - the previou
Marcel van der Boom writes:
> 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 th
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
