Jira : PDF template export linked issue

[Arthur SALMON]

Hi community,

I would like to create a new template for PDF export in order to include all linked issue "blocked by" when I export the blocking issue.

Actually, what happens is my user is filtering with JQL to retrieve all blocking issues in his EPIC and he has to export those issues with the "blocked by" linked issue but he has to do the linked issues one by one currently.

Would you have any idea on how to do that (I was thinking best way would be to create a new template for pdf export)

I am currently on Jira v7.13.2 and planned to migrate on last enterprise version.

Thanks in advance,

Arthur

[Aron Gombas _Midori_ · Accepted solution]

Are you using an app to create the PDF output? (If it is the Better PDF Exporter app, then I could help.)

[Arthur SALMON]

Hi,

Yes I use better PDF exporter.

[Aron Gombas _Midori_]

OK, then I think you should write a JQL that collects the "origin issue" and the linked issues using the corresponding JQL function, something like this:

key = FOO-1 or linkedIssues(FOO-1,"is blocked by")

 It will return FOO-1 and all issues blocked by this.

Then you can export the issues from the Issue Navigator with some clicks.

It may not be 100% what you want and I haven't tested it, but this should give you the idea. Also, see the JQL function doc.

[Arthur SALMON]

Thank you Aron, I am going to test that.

I will probably have to go deeper for what we want. The current JQL we are using to export the parent was : project = "my project" AND "Epic Link" = KEY-622

So my first thought is, with JQL, I will not be able to export the PDF with all parent issue contained in the EPIC and with all issue linked to those parents with a good render, this is why I thought of using the PDF templates.

[Arthur SALMON]

Hi Aron,

I haven't found yet how to do it completely. If I do it only with JQL, I can retrieve all the parent issues containing the links "blocks" and I can retrieve the child issue using the parent issue key and linked issue tag but so far I am not able to retrieve all the child issues at once contained in the EPIC.

I was thinking doing a loop in the template on all parent issues found in the Epic to retrieve all the child. What is your thought on that ?

Thanks,

Arthur

[Aron Gombas _Midori_]

I'd still try to do it in JQL (although the approach that you program it in the template could also work). There are several topics here in the community site that discuss use cases similar to yours.

For example:

1. https://community.atlassian.com/t5/Jira-Software-questions/JQL-to-show-all-issues-AND-subtasks-in-the-Epic/qaq-p/346433
2. https://community.atlassian.com/t5/Jira-questions/JQL-query-to-find-issues-of-epics/qaq-p/362826
3. https://community.atlassian.com/t5/Jira-questions/How-to-get-a-list-of-quot-issues-in-epic-quot-in-Jira/qaq-p/511549

These or similar others should help...

[Arthur SALMON]

Hi Aron,

Thanks to you, I might have found my answer, I will check with my colleague if it answer to his need.

The function would be : project = FOO-1 AND issueFunction in linkedIssuesOf("\"Epic Link\" = BAR-1", blocks) OR ("Epic Link" = BAR-1 AND issue in hasLink(blocks))

What I need to validate with my colleague is he can export it the way he wants. Which is not sure.

Thanks for the help,

[Rina Nir]

Hello @Arthur SALMON ,

I know your question is resolved, but wanted to suggest one way to solve this (and similar situations), for the sake of future readers.

If you also have Confluence, then you could use the app Jira Snapshots for Confluence to generate this static report in Confluence. To achieve this you would (once the app is installed on your confluence):
1. Add a "Jira Snapshots" macro top the page where you need this report

2. Define the first level: so use the first JQL to retrieve all the stories in the Epic , ie: "Epic Link" = BAR-1
3. Then define the second level, where you get the issues blocked by each of the issues in the first level, respectively: issue in linkedIssues($key,"is blocked by")

The advantage here is that no programming or scripting is required, and you can embed this table in any layout of a confluence page.

As in PSF- once you take the snapshot- the data is static and reflects Jira data at the point in time