On 20 Jun, 2008, at 17:17 , isoaglib wrote:
> Hi,
> I tried the following:
> story.task.calculate = total_remaining_time=sum:remaining_time ,
> total_estimatedhours=sum:estimatedhours
> to get also the sum of estimated hours.
> But the result value, that is displayed in total_estimatedhours is the
> same as "sum:remaining_time".
> Defining both in separate lines results in a correct display of
> total_estimatedhours - while now no total_remaining_time is displayed
> at all.
It should work we have a test for it, and actually a customer using it
with actual_time and remaining_time, can you send your trac.ini so
that we can test it?
> By the way - the documentation indicates source.destination.calculate
> - but in the working example from the docs, source:=task -
> destination:=destination - or not??
if there is a link defined as:
allowed = story-task
means that the source is the story and the destination is the link,
link are directional. Therefore if you write a calculate as:
story.task.calculate = total_remaining_time=sum:remaining_time
Story is the source of the link, Task is the destination, and the
expression is aggregating (sum is the only operator at the moment, the
percent from source to destination is planned) the property
remaining_time of the task into a "virtual" property
"total_remaining_time" on the story.
> ==> Please fix the documentation for source, destination _AND_ give
> hint on how to add TWO and more calculated
> fields
They should just work, I'll check again not to have broken the feature
with 0.6.3 would be strange, because we have a test for it... but you
never know :-? The documentation is ok, where is the problem?
> ##
> The docs mention the issue type "impediment" - but how can I use and
> configure it?
Impediment are used by Scrum Master to trac the issue that are
blocking the team and need to be fixed, they can be configured, adding
the type in trac, from webadmin for example, and configuring it into
agilo-types in the trac.ini
> Thanks,
YAW
> Achim
ANdreaT
