Problem with more than one calculated field per trac-type _AND_ what about impediment

[isoaglib]

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.

By the way - the documentation indicates source.destination.calculate
- but in the working example from the docs, source:=task -
destination:=destination - or not??

==> Please fix the documentation for source, destination _AND_ give
hint on how to add TWO and more calculated
fields

##
The docs mention the issue type "impediment" - but how can I use and
configure it?

Thanks,
Achim

[isoaglib]

Hi,
I tried to add referencing between tasks --> to get dependency between
some tasks.
This works basically.

But now I would need a more flexible approach for the calculation -
where I can assign the sum of more than one source field to one target
field. This way I could propagate the values up to the root - even
with a sequence of tasks at the lower level.

Thanks,
Achim

[Andrea Tomasini]

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

[ANdreaT]

> 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?

Error! :-? We have a test in the 0.7 and works, in the 0.6 doesn't I
can make a back porting, I'll check if possible, or you can wait till
0.7 will be released ;-)

Best
ANdreaT

[Andrea Tomasini]

I should have fixed it now... I made a 0.6.4 for that... and some
other little things ;-)

Let me know if it works :-)

Best
ANdreaT

[ANdreaT]

Any news here? Can we change the subject to FIXED?

Thanks
ANdreaT