importance defaulting to 50%

[David Rees]

Andrey,

 

Do we have a feature # for getting the default importance back to 50% for hierarchical? I know Bob has said its possible with some thinking and it’s a serious issue (basically users are forced to use the urgency slider for any kind of adjustments).

 

Thanks,

 

d

[iLiAS]

I agree with this. Thanks for bringing it up David. It was discussed a
while back in detail, but that discussion has sort of died down.

I think this is a rather *big* issue with MLO at the moment. My
understanding is that the default (max) priority has a computational
factor of "1", and lowering it affects the computed score of the
subtasks. This, of course, is desired. The *problem* is that this has a
*cumulative* effect on the subtasks, and it becomes more severe the
deeper the branch is. I have some branches that are quite deep, but I
keep the top-level task of the branch as "max" priority (although it is
not) just so that I will not completely compromize the computed score
of the deeper-level tasks. Not good.

Any thoughts on this Andrey?

Cheers,

-ilias

[Andrey Tkachuk (MLO)]

>Any thoughts on this Andrey?

Will work on this when Bob has more time.

[Bob Pankratz]

Ding.....

Still here....

Couple more weeks of heads done on the transition.....