Define additional Fields to aggregate Information (number Fields), e.g. suggested revenue
We use structure for many purposes like:
Artifact Structures (Epic, Story, Reqs) oder product based views on many projects. So it would be very useful if one can define a field in a strcuture, that ist aggregated to its parents (if possible) likewise the time aggregation.
There could be a Aggregate Field be defined, that uses the Value(numbered) from a custom field and aggregates it to the parent with options for the aggregates (sum, avg, max,min)
Done in version 2.5: https://wiki.almworks.com/x/3ILR
-
anh commented
Same request here: we would like to track two different types of estimates. One from an early stage in the process (Epic level, in Story Points) and the other one on Story level (also in Story Points, e.g. using the standard GH field for it).
Both we would like to be able to see aggregated in the sturcuture view (calculated rollup).
-
Thanks! We've already thought of that and have a nice UI solution. Stay put! :)
-
Andreas Haaken commented
Maybe it might be helpful, if one could define which columns(fields) should be aggregatable per structure. I f there are a lot of numeric fields, it could be overloaded if avery num-field is offererd as aggregate :)
-
Thanks, Andreas! We'll work on this.
-
Andreas Haaken commented
Well a Column would be enough for our purpose.
I Think the main thing is that one can define a numeric field for an issuetype and have this one aggregated in a structure.e.g
Issuetype=Vacation
Numeric field= duration(in days)and a structure is defined as list of employees with vacations as children and then calculate the sum of vacation days on every employee
this is just a fictive scenario, but it shows the needs. real world ones would be populated around economic views on a project or for strategic views
-
Andreas, thanks for your idea!
We're planning to add aggregation to all numeric fields, so like with the estimates, you'll be able to show the column with aggregate number.
However, we don't plan yet to have a custom field that would store this custom data -- do you really need a custom field? Or a column on a structure grid would be sufficient?
Igor