Unable to print Sub-tasks of an Issue.

[Tarun Sapra]

Hi,

In greenhopper, while using Agile Cards plugin, we are not able to get the sub-task informaiton on the generated PDF, only the parent issue informaiton is there. Isn't there a way that while printing an issue all of it's sub-tasks also get printed?

In the Agile-cards plugin configuraiton i have ticket print subtask option as well, still it doesn't seem to work.

Edit - I just saw this link - https://jira.atlassian.com/browse/GHS-4451

is there some way to achieve printing of the sub-tasks?

Thanks,

[Midori · Accepted solution]

Alternative: print your story cards using the JIRA PDF View Plugin.

This plugin renders PDF documents from issues, based on templates (you can define the document layout, look, and what content to print), optionally executing additional logic (in form of Groovy scripts). These make it a really poweful tool to generate any kind of documents from JIRA data, including agile cards, too.

See: Sample card - the default template set includes this simplistic story card template that is a good starting point for further customization (if needed)

[Ramya Mure]

Hi Ferenc, I am using PDF View Plugin currently to generate PDF reports and it works pretty good.
But I have a requirement like the question posted: Is there anyway we can print information of all the related sub-tasks of a main task, within the same PDF document. I really need to make this happen, so if you have inputs for this, do please let me know.

[AhmadDanial]

Hey there, Tarun.

In regards to the Agile Cards plugin, we would recommend you to contact the plugin vendor directly to speed things up on your side. They will be the best point of contact when it comes to the plugin usability itself. Kindly refer to the following:

• Name: Spartez
• Address: ul. Na Zboczu 33, Gdansk 80-110, Poland
• Email: mail@spartez.com
• Phone: +48 58 719 22 94

Referring to the https://jira.atlassian.com/browse/GHS-4451 ticket that you mentioned, it is still in the Open state. Hence, it might take quite some time before it gets looked at by the developers before it get implemented. Kindly refer to the Atlassian's Implementation of New Features Policy (http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy) for further information.

Warm regards,

Danial