Hi Steve, Building on David's suggestions, once you have the summed values (either way), you could then manually update those amounts in numeric custom parameters at the Task level. Stored as such, you could then do all of the usual kinds of things with it: report on them, chart them, even refer to them in calculated data (e.g. on the Issue level, you could create a calculated parameter that shows the % contribution that each Issue made as a portion of the total at the Task level). Where it gets really interesting, though, is to automate such calculations using either the API or our "http://store.atappstore.com/product/ubercalc/">UberCalc solution. We developed a similar technique to:
take the data driven "value weightings" (e.g. 0 to 100) of each Project within a Portfolio
take the average of all Projects within each Portfolio and store it in a special Average Project Value (APV) custom parameter
use advanced conditional formatting to highlight those Projects whose value weighting is above (green), near (yellow) or below (red) APV
Noting that the value weightings were ever changing (and of course, new Projects appeared continually), doing so then made it possible to prioritize and focus on "today's" most valuable Portfolios, and within that, "today's" most valuable Projects, and obvious when to move on (yellow/red) to the next Portfolio. Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand!
https://community.workfront.com/participate/unanswered-threads