Ability to group issues hierarchy in a correct way for multiple selection fields#45

The feature to be able to group on fields is great but it is not possible to do this in a correct way for multi selection fields and/or cascading dropdown fields.

For example if you want to group on Components and multiple values are selected it will be added as a new group. See the example below.

Currently:
Component 1 (10 items)
Component 2 (5 Items)
Component 1 Component2 (5 items)

Expected:
Component 1 (15 items)
Component 2 (10 Items)

Hi Bernie, thanks for your feedback!

One question: say we implement the way you suggested, there is a chance that an issue will appear multiple times in the table. For example, the 5 items associated with Component 1 and Component 2 will appear twice - once under the group “Component 1”, and a another in the “Component 2” group.

Under such situations, would you expect the app to sum-up all the field values, even if they are duplicates? E.g. Issue A has 3 story points and is associated with Component 1 and Component 2. It appears once for each group. Should the sum-up be 3 story points, or 6?

Regarding the (xx Items) that is just to explain) but to keep it simple I would say, count it as double and if possible add a hover over popup on the total number to show the number of points coming from single linked group and how many points from double linked groups. This way it will be visible. It also makes it possible for the user to take out the double calculated points if needed.

Other to this, I would advice to add a tickbox next to the group field so that the user is able to decide if the overview needs to see multiple groups as a separate group or not.

That is clear now, thank you Bernie. Having the option to enable or disable combined groups makes sense too. Moving this ticket to the next stage :)