John Sullivan wrote:
> Sounds like the correct behavior to me. Planner does not check when
> you create a new task to see whether the description is the same as
> one that already exists. Each new task created gets a new ID.
Well, the problem is that on the plan page, if the new task has the
same description as an already existing task, it doesn't get an ID at
all, and the old task gets the new ID. This is on the plan page; on
the day page(s), the tasks get and keep their IDs as they should.
> If you want to make copies of tasks and have them all have the same ID,
I'm sorry if I was unclear about what I wanted: I want the exact
opposite: Two or more tasks with unique IDs, but the same task
description, i.e.:
What I want is the following:
In the plan page:
#B _ My fine task {{Tasks:13}} ([[2006.10.04]])
#B _ My fine task {{Tasks:14}} ([[2006.10.05]])
in 2006.10.04:
#B _ My fine task {{Tasks:13}} ([[TaskPool]])
and in 2006.10.05:
#B _ My fine task {{Tasks:14}} ([[TaskPool]])
> Can I ask what the use for this is?
I often have long tasks that I need to split into sub-tasks, but I'd
prefer not to give the sub-tasks separate names (descriptions). And
sometimes I can't tell in advance how many sub-tasks I will need. An
example: The long task: "Try to prove that leave-one-out jackknife has
property foo". I would like to schedule this task on several days,
because I believe it will take some hours to finish (or to fail :-).
I could schedule it today's page, and then just move it forward every
day until it is finished, but that makes it harder to plan the rest of
the week, and afterwards, the day pages don't show what I've been
doing that day, only what happened to be finished that day.
> Also, can you describe the case more when it did work as you
> expected?
Unfortunately not, since there is no case when it works as I hoped. :-)
--
Bjørn-Helge Mevik
_______________________________________________
Planner-el-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/planner-el-discuss
