Modify a JQL Query so that multiple rows data can be merged as single row on basis of common parent

[Abhishek Ashok Dingre]

Hi All,

I have a scenario, wherein I have a JQL Query which fetches records of all epics contained in one parent which in my case is a sub-step

All epics are showed as individual rows under the JQL query and under each row I can see the respective application efforts.

I have a requirement where I need to club all these different rows and show them as 1 row and my individual application efforts should be appended and shown as 1 effort.

How can I modify a JQL Query to merge all rows and show them as 1 row?

Kindly note that I am looking to merge all data as a single row on basis of the parent sub step. As this parent sub step will have multiple epics and each epic will have the details of application efforts.

Example we have a parent as "ABC" and under that parent we have an epic X which has app effort with name as "E1" as 20. I have another epic Y which has same app "E1" and that app has effort as 40.

Now, instead of showing 2 different rows. I need 1 row to show the effort under the parent "ABC" as 60

Ay suggestions please?.. thanks for your help.

Regards

Abhishek

[Walter Buggenhout]

Hi @Abhishek Ashok Dingre,

Short answer: that is not possible with JQL.

With plans (and marketplace apps like e.g. Structure) you can build views where efforts are rolled up nicely across your issue hierarchy. But JQL returns a list of issues matching the criteria you specify; it does not let you aggregate information from multiple issues.

Hope this helps! 

[Dmitry Astapkovich _Colined_]

Hi @Abhishek Ashok Dingre ,

As @Walter Buggenhout  mentioned above, it's not doable with JQL. You would need a Marketplace app for that, e.g. Pivot Report that we develop. Here's a demo report to illustrate how it works for your case:

Basically, there are 2 views in the report (it's customizable). One shows the custom hierarchy based on issue link (can be Advanced Roadmaps as well), another one is a Pivot Table where all estimates are rolled up to the Top Parent and then split by Assignee (optional). 

I hope that covers it. Feel free to play with the report on your own or let me know   if you need a demo call: da@colined.com