How to use total progress calculation when using grouped issues

[Esteban Chong Chow]

According with Jira-Structure documentation for "Total Progress Calculation" at https://wiki.almworks.com/documentation/structure/9.1/cloud/progress-column-130883892.html you can specify how sub-issues progresses are aggregated into parent issue progress. But, when trying to group issues by Projects and using a numeric field to weight each "epic" issue, the calculation rolling up to the grouped line is not correct since the weighted progress uses not only the weights per each "epic" but also any other weight under sub-issues (histories, tasks and subtasks).  
See the following calculation that is wrongly calculated for the grouped line (image #1 - Key CJC) showing 27%, against the workaround calculation (image #2 - Key CJC) showing 5%.

The problem we see is that when you group issues, the total progress calculation under an "issue progress based on field and weighted" the weights for the grouped line item considers all lines were there are weights included.

Has anybody solved this problem with.  The workaround was to weight with round numbers the epics and to weight with decimals the sub-issues. (See image #2).   

 Image #1 - Wrongly calculated 

Image #2 - Work around

[Mariia Romanova · Accepted solution]

The issue you're encountering with  Structure plugin seems to be related to how the total progress calculation is configured when using weights. Probably you will find the unswer here  where they describe how is calculated total progress and individual , and what value is taken into account when one of these values (numeric field or time tracking) is empty. 

[Esteban Chong Chow]

Thank you for your reply. The total progress calculation as refered under https://wiki.almworks.com/display/structure056/Progress+Based+on+Percent+Field works as documented. The problem is when Top Issues are grouped under a Field e.g. by Project and Total progress calculation is needed taking all Top Issues that currently won't calculate as expected.  
Current weight under a numeric field seems to be behaving as the story points field or other custom field (cumulatively).  We need another way to use current 0 to 100 weights for parents with sub-issues but to calculate total progress for a group of only Top Issues without using data from weight fields from sub-Issues.

On the same structure we have weighted progress for epics different from those for histories and tasks.

[Mariia Romanova]

In your case I found it very clever to use decimal to avoid double counting by weight. And on your second picture the total progress seems to be more correct than on the first one. I guess you are right about  that it behave as if it were Story point custom field. And on the first picture-  we see that total weight for sub-issues is much higher than total weight of Epic that contains those story with sub-issues. ( I guess the problem is also that sub-issue can’t have weight more than epic by itself , because weight of epic = sum of weights of all issues entering this epic . In your case I see that epic has 10, but total weight of sub issues is 100.  So projects total progress is calculated  as of weight =200… try to change values of weight of sub issues as ( 5, 3, 1, 1 ) instead of 50, 30,10,10. 

[Esteban Chong Chow]

Yup, works fine now.  Using a numeric field to weight progress on a "total progress calculation" when grouping Top Issues has to be used to add up 100 including all issues (parents and childs).  Doing this, then it seems to calculate as expected. But, small but, key CJC-33 and key CJC-39 has to be empty since sub-issues have been weighted, otherwise, if populated with weight, they will be added twice or tripled.

Thank you.

Esteban