How to display those 'Child issues' OR 'Issues in EPIC' in Confluence ??

[Ramu]

Dear All,

I'm aware of how to get the child issues in JQL using quite few ways (issue in childissuesof, parentepic() ..etc )..

My real question/prob where i stuck is 'How to display those 'Child issues'  OR   'Issues in EPIC'  in Confluence ?? (Im not talking about the Linked issues or Issue Links which is an easy and straight forward one)

u

Confluence:

I have a need to display all the JIRA EPICs and associated CHILD issues(again not the Linked issues please) .. in a Confluence TABLE

like .. Column1(EPICS), Column2(CHILD Issues of the EPICs) ..

i dont see an option to get this(Child issues or Issues in EPIC) in Confluence ... the only option im trying is to do a Table Transformation macro but still im exploring and yet to find a way in that well ..

I strongly believe and hope that i will get a help here from you all .. Please help.

[Matt Parks · Accepted solution]

You could create a Roadmap/Plan in Jira with the appropriate Epics and their children and then use the Advanced Roadmaps for Jira in Confluence macro to display the Plan. If you go that route, you need to get the URL for the Plan in a specific way (not just copying the URL from Jira), but I can give you that information if you need it.

Another option, if you have Structure for both Jira and Confluence would be to create a Structure in Jira and then use the Structure macro in Confluence to display it.

[Ramu]

Thanks Matt .. 

The challenge is that all these came as requirement to me to work out and find a solution which in turn means, all these are diff projects already existing and i cant go from scratch (not that i dont want to but there are thousands of EPICs across multiple different Space/Projects already)

While i understand the Roadmap one, the setup we have is already existing for years now and i dont have the authority to change and go for Roadmap as there quote plenty of different projects involved from different Space areas.

I'll check for this Structure Macro but like i said all these were not structured properly at the initial phase itself i doubt it .. still i'll atleast check what it is and see ..

Cheers .. 

[Matt Parks]

Are you able to run a single query that will return all of the epics that you would want to see in the table? If not, I don't see any other way of doing this besides manually creating a table in Confluence.

Even if you are able to run a single query that returns all of the epics, I'm not sure how you could include the stories in the plan unless you have either Structure for Jira or Scriptrunner, which provides additional JQL functions. With that information, you'd be able to create a query that you could use to populate a Roadmap.

[Trudy Claspill · Accepted solution]

Hello @Ramu 

Welcome to the Atlassian community.

You may have noticed that Jira provides a column/field for displaying a list of the issue keys of Linked Issues. Unfortunately there is not a comparable column/field for display a list of the issue keys for Child Issues.

You might be able to find a third party app that would add such a custom field to the Jira system.

Or you might be able to develop a work around that uses Automation Rules to gather that list of Child issue Keys and paste the the list into a custom Text (or Paragraph) field that you add to the Epic issue types.

[Ramu]

Hi @Trudy Claspill  .. Thank you for the response .. Automation rules is something i can think of but again cant pass through the Confluence restriction .. i'm also exploring on this ... will see if i get any more alternate thought further ... Thanks for yours :)

[Trudy Claspill]

I'm not sure what you mean by "again can't pass through the Confluence restriction".

You would be running an Automation Rule in Jira to fill in a custom field in the Epics with a list of the child issue keys.

In the Jira macro in Confluence you would then include that custom field in the fields you select for display.

Doesn't that satisfy your requirement?

You did not specify if you are using Jira and Confluence Cloud or Jira and Confluence Server/Data Center. I know this method would work for Jira Cloud. The Automation Rules capabilities for Jira Server/Data Center are not as extensive so I don't know for sure that the Automation Rule could be constructed there.

[Ramu]

Yes .. the JIRA/Confluence at our organization(Data Center) has restrictions ..  im an admin but not like Super Admin .. for example, i cant get the more than 1000 rows/records displayed in Confluence whereas, a Super Admin can ... just one example i meant

Reg: Automation .. yes the custom field is fine (anything in JIRA is fine and doable for me) but calling that out in Confluence ..i have restrictions in Confluence.. as custom fields display is not possible to my knowledge ..

thats when i decided to approach here to see any alternate.

[Trudy Claspill]

To the best of my knowledge there is no restriction on displaying custom fields as part of a Jira/Issues Filter macro in Confluence Data Center. All you should need to do is place your cursor in the Columns to Display field and start typing in the name of the field you want.

I am, however, a full Confluence Admin and Jira System/Application Admin in my environment.

[Ramu]

:)  :)   ...

please check the screen trailing:

i mean there is no direct field available in Confluence to call out the 'CHILD  issues'   OR   'issues in EPIC' other than 'Linked Issues' ...

To summarise, i'm in a high time need of bringing the following(Display of CHild issues of the corresponding EPICs) in a Confluence Table:

-  There is no 'Structure Macro' available (restricted) in my Confluence ..

-  Though im not expertise in automation, still to my try outs/knowledge, fetching the Child issues from JIRA EPICS and displaying in Confluence ..looks almost not possible .. like i mentioned above, calling that field in Confluence is not there. 

-  Im still try exploring Table Transformation(trust me .. it works) .. but the challenge with this one is that it takes hell lot of time to load and doing a small modification also, takes like hours (reason being it fetches/queries 1000+ records as the result) ..

coz of it's latency and load, displaying/navigating in our calls is not feasible as the entire schedule time gets over for this to load ..(not that we have cheap network .. but trust me Table transformation is known for its high load time issues when your data is more than 1000 records).

Now, having said all these ..

i still believe there is a way which you   or   any expertise/masters in this forum can enlighten/help .. I'm requesting on the same please ...

[Trudy Claspill]

As I said before:

Or you might be able to develop a work around that uses Automation Rules to gather that list of Child issue Keys and paste the the list into a custom Text (or Paragraph) field that you add to the Epic issue types.

Here is an example of a rule that would accomplish this.

This rule runs on a schedule. Once a day it gets a list of the Epics in the project and then updates the field in each Epic that holds the list of child issues.

In this rule I am using the Description field. You would need to first have a custom Text or Paragraph field created that you could use to hold the list of child issues.

The trigger retrieves a list of Epics. With a Scheduled trigger, the remaining steps in the rule will be executed as a set for each issue found by the trigger. The rule iterates over the list of issues found by the trigger.

The Lookup Issues action gets the list of child issues of the Epic of the current iteration.

The conditions in the If and Else-if used Advanced Compares to compare a smart value (the count of results from the Lookup Issue action).

In the If, the rule checks if the results count is zero. If it is, the Edit action will clear the custom field in the Epic where the child issue keys are stored.

In the If-else, the rule checks if there is 1 or more issues in the results set of the Lookup Issue action. if there is, then if first edits the Epic to clear the custom field, then it edits the Epic again to set the custom field to the current list of child issues.

The step to set the field to the list of child issue keys looks like this:

And the end result looks like this:

Then in Confluence with a Jira Issues/Filter macro you can add the custom field you created where you have stored the list of child issues in the Epic.

[Ramu]

Thank you so much @Trudy Claspill  .. i'll give a try on this and will keep it posted here ...for sure ..

[Ramu]

Hi @Trudy Claspill  ..

Sorry it took time for me to respond back(not intentional) ..

I'm able to accomplish this through QlikSense as we have started using it recently .. Thanks for your guidance and support ... especially your ideas of different try outs .. Thanks again :)

[Jan Denny]

Are there any plans for Atlassian to add a field to the Epic issue type that would be aware of all the Epic's child stories / tasks? I suspect that if this were implemented, it would enable a lot of other customizations - like perhaps using Templates to generate child issues when an Epic is created if this "child issue" field could be populated in the template to point to templates for the child issues.

[Ramu]

Given the Confluence restrictions i have in terms of not having 'Structure macro' in my Confluence, unable to callout the custom fields etc ..

Still trying my luck with 'Table Transformation' only.

I have a need to display all the JIRA EPICs and associated CHILD issues(not the Linked issues please) .. in a Confluence TABLE

like ..

Column1(EPICS), Column2(CHILD Issues of the EPICs) .. in a Confluence Table ..

Please share your inputs/thoughts