Discussion:
[Agilo for Trac] Calculated properties - subtration
hamsteg
2014-08-27 12:10:14 UTC
Permalink
For calculated properties the basic operator lacks subtraction.

sum, mul and div are implemented but that last basis operator is not. Why
need it? Well because filtering on !=/=! is not possible.

I have a multi-level product backlog. Apart from the tasks each level has a
size indication / story points. I can calculate the sum of all sizes but
this includes the closed stories. Preferably I would like to add a filter
"|status=!closed" but that seems impossible according to other postings. So
I will count the total product backlog size and the product backlog size
for closed stories and subtract them ...

How to get rid of the closed sizes?
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
Stefano Rago
2014-09-01 07:32:44 UTC
Permalink
Hi there,
Post by hamsteg
For calculated properties the basic operator lacks subtraction.
sum, mul and div are implemented but that last basis operator is not. Why need it? Well because filtering on !=/=! is not possible.
I have a multi-level product backlog. Apart from the tasks each level has a size indication / story points. I can calculate the sum of all sizes but this includes the closed stories. Preferably I would like to add a filter "|status=!closed" but that seems impossible according to other postings. So I will count the total product backlog size and the product backlog size for closed stories and subtract them ...
How to get rid of the closed sizes?
Backlogs of type 'global' can be configured to automatically hide tickets that have been assigned to a sprint or milestone, and such tickets won't be taken into account when calculating properties.
If a story is closed, it's probably because it has been planned first, so it should not appear in the backlog anymore.

Perhaps you have configured the backlog to include planned items?

You can check that by logging in with TRAC_ADMIN permissions, going to the 'Admin' panel, click on Backlogs under the Agilo section and select your backlog.

Hope this helps

Cheers,

Stefano Rago
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.

To post to this group, send email to agilo-/***@public.gmane.org
To unsubscribe from this group, send an email to
agilo+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/agilo

---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
Loading...