[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [PATCH 07/10] org-taskjuggler: make project umbrella task option
From: |
Yann Hodique |
Subject: |
Re: [O] [PATCH 07/10] org-taskjuggler: make project umbrella task optional |
Date: |
Sun, 12 Aug 2012 10:03:28 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.1 (darwin) |
>>>>> "Christian" == Christian Egli <address@hidden> writes:
> Yann Hodique <address@hidden> writes:
>> +(defcustom org-export-taskjuggler-keep-project-as-task t
>> + "Whether to keep the project headline as an umbrella task for
>> + all declared tasks. Setting this to nil will allow maintaining
>> + completely separated task buckets, while still sharing the same
>> + resources pool."
> I'm trying to understand the use case here. If I understand correctly
> the container headline will no longer unconditionally generate a root
> task. So you could have multiple root tasks? Does this work in both
> versions of tj?
Yes, basically the use case is the following.
>From an org code like:
--8<---------------cut here---------------start------------->8---
* Main :taskjuggler_project:
** Task1
** Task2
--8<---------------cut here---------------end--------------->8---
the default behavior is to generate something like
--8<---------------cut here---------------start------------->8---
project main Main (}
task main "Main" {
task task1 "Task1" {}
task task2 "Task2" {}
}
--8<---------------cut here---------------end--------------->8---
leading to a report like
--8<---------------cut here---------------start------------->8---
1. Main
1.1 Task1
1.2 Taks2
--8<---------------cut here---------------end--------------->8---
while the new (non-default) one would generate
--8<---------------cut here---------------start------------->8---
project main Main {}
task task1 "Task1" {}
task task2 "Task2" {}
--8<---------------cut here---------------end--------------->8---
leading to a report like
--8<---------------cut here---------------start------------->8---
1 Task1
2 Task2
--8<---------------cut here---------------end--------------->8---
I must confess this is mostly a way to avoid questions from people
looking at the report, asking why my task numbers are all 1.x :)
AFAICT it seems to work fine with either tj2 or tj3. I'm using tj3 only
myself, but the UI of tj2 doesn't complain at all about those multiple
root tasks.
Thanks,
Yann
--
When faced with necessary actions, there are always choices. So long as the
job gets done.
-- COUNT HASIMIR FENRING, Dispatches from Arrakis
- [O] [PATCH 00/10] Takjuggler exporter improvements, Yann Hodique, 2012/08/05
- [O] [PATCH 01/10] org-taskjuggler: make task and resource properties customizable, Yann Hodique, 2012/08/05
- [O] [PATCH 04/10] org-taskjuggler: task with end-only is also a milestone (deadline), Yann Hodique, 2012/08/05
- [O] [PATCH 02/10] org-taskjuggler: properly install local variables at export time, Yann Hodique, 2012/08/05
- [O] [PATCH 03/10] org-taskjuggler: make use of org properties, Yann Hodique, 2012/08/05
- [O] [PATCH 05/10] org-taskjuggler: introduce a global header, for early macros, Yann Hodique, 2012/08/05
- [O] [PATCH 06/10] org-taskjuggler: use project end date, if specified, Yann Hodique, 2012/08/05
- [O] [PATCH 07/10] org-taskjuggler: make project umbrella task optional, Yann Hodique, 2012/08/05
[O] [PATCH 08/10] org-taskjuggler: disambiguate "headline", as it's also a valid taskjuggler property, Yann Hodique, 2012/08/05
[O] [PATCH 09/10] org-taskjuggler: allow reports definition from within the org file, Yann Hodique, 2012/08/05
[O] [PATCH 10/10] org-taskjuggler: update doc to reflect latest changes, Yann Hodique, 2012/08/05
Re: [O] [PATCH 00/10] Takjuggler exporter improvements, Bastien, 2012/08/05