|
| |||||||||||||||||||||||||||||||||||||
 | PDF View Plugin 0.9.3 Released. In this version, templates made more fault tolerant. |
Description / Features
This plugin adds a new view type "PDF" to the existing ones ("XML", "Word" and such). When clicking it, it renders PDF documents from a single issue or from a list of issues (like the result set of a search request or filter, release notes, etc.). It can be used for static exports or for hi-quality paper prints.
- Fast: it's just one click to get your PDF.
- Efficient: you can freely customize the content (what to print) and the layout (how to print).
- Nice: it does not rely on the limited printing and page breaking capabilities of the browser.
Usage is Simple
- Install the plugin as described below.
- There will be new links appearing in the following screens:
- Issue Navigator (after a firing a search request, running a report or such)
- Issue Details
- Click on these links to download the PDF documents.
Installation
- Download the JIRA PDF View Plugin ZIP file.
- Unpack the ZIP archive and install the following files:
- Copy the plug-in JAR file jira-pdfview-plugin-xxx.jar to the JIRA_HOME/atlassian-jira/WEB-INF/lib directory.
- Copy the plugin dependency JAR files from the lib directory to the JIRA_HOME/atlassian-jira/WEB-INF/lib directory, unless you have a compatible version of those JARs there.
- Copy the content of the classes dir to the JIRA_HOME/atlassian-jira/WEB-INF/classes directory. This will copy 3 types of files:
- Regular Java class files. These 2 files are already existing in the target directory, so you will have to overwrite the existing ones. Please note that with this step, you effectively patch those 2 JIRA classes, so we strongy recommend making a backup of your original .class files before you overwrite them. (See the FAQ for more details about why it is necessary.)
- Template files. (Those with .vm file extensions.)
- Additional configuration files like fop-config.xml.
- Very likely you want to change the system logging settings to avoid the annoying table-layout="auto" is currently not supported by FOP warnings: learn more here.
- Restart JIRA.
- Make sure that a new view type PDF is visible in Issue Navigator and in the Issue Details form. (See the Screenshots section if it's unclear where you should look for them.)
Screenshots
|
Screenshots (view as slideshow) |
||||
|---|---|---|---|---|
|
|
|||
Configuration
All the plugin, PDF content and layout is highly configurable, please read Configuring and Customizing JIRA PDF View.
Version History
| Ver. | Date | Notes | |
|---|---|---|---|
| 0.9.4 | 12062008 | More detailed logging to help troubleshooting. | |
| 0.9.3 | 26042008 | More fault tolerant templates. | Release Notes & Upgrade Guide |
| 0.9.2 | 24042008 | Search request views fixed. | Release Notes & Upgrade Guide |
| 0.9.1 | 18042008 | Custom fields. | Release Notes & Upgrade Guide |
| 0.9-beta | 29012008 | Multiple views. | |
| 0.8-rc1 | 15012008 | More fault tolerant templates. | |
| 0.8-preview | 09012008 | First preview release. |
FAQ
Q: Why must JIRA be patched? Isn't it dangerous?
A: Currently (as of version 3.12), JIRA supports views that return String content only, no binary content is supported. PDF files are binary, so the patch must be applied, then JIRA will return the bytes correctly for the browser. This is a rather simple modification and is safe.
If this limitation gets resolved in future JIRA versions, the patch won't be necessary anymore. Please vote for this issue to help us.
Q: I see Warning(35/76): fo:table, table-layout="auto" is currently not supported by FOP lines in my log, but the PDFs look good.
A: Those warnings are coming from FOP (and are related to a missing feature), but don't have any effect here. You can ignore them.
If you prefer not logging those warnings, then add the following lines to JIRA_HOME/atlassian-jira/WEB-INF/classes/log4j.properties and restart JIRA:
##################################################### # CLASS-SPECIFIC LOGGING LEVELS ##################################################### ## ... there is stuff defined here, leave that unchanged and add these 2 lines to the end of this section log4j.category.org.apache.fop.fo.FONode = ERROR, console, filelog log4j.additivity.org.apache.fop.fo.FONode = false
Q: I'm am using 0.8 and I am customizing my issue-fo.vm template, but I have to restart my container (Tomcat) every time when I want to see my changes, and it's highly inproductive. Is there a way to eliminate the need for restart?
A: Yes. issue-fo.vm is loaded through the standard Velocity template manager of JIRA, which can be configured editing JIRA_HOME/WEB-INF/classes/velocity.properties. You can disable caching the templates by commenting out this section (please ignore what the comments say):
resource.loader=class class.resource.loader.description=Velocity Classpath Resource Loader class.resource.loader.class=org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader # To enable autoreloading, set cache to false and uncomment the autoreload line class.resource.loader.cache=true #velocimacro.library.autoreload=true class.resource.loader.modificationCheckInterval=0
...and pasting this instead:
resource.loader=file file.resource.loader.description=Velocity File Resource Loader file.resource.loader.class=org.apache.velocity.runtime.resource.loader.FileResourceLoader file.resource.loader.cache=false file.resource.loader.modificationCheckInterval=1 file.resource.loader.path=<path to your JIRA_HOME//WEB-INF/classes dir>
So finally it looks like this:
# original configuration # resource.loader=class # # class.resource.loader.description=Velocity Classpath Resource Loader # class.resource.loader.class=org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader # # To enable autoreloading, set cache to false and uncomment the autoreload line # class.resource.loader.cache=true # #velocimacro.library.autoreload=true # class.resource.loader.modificationCheckInterval=0 # auto-reloading templates resource.loader=file file.resource.loader.description=Velocity File Resource Loader file.resource.loader.class=org.apache.velocity.runtime.resource.loader.FileResourceLoader file.resource.loader.cache=false file.resource.loader.modificationCheckInterval=1 file.resource.loader.path=/java/apache-tomcat-5.5.25/webapps/atlassian-jira/WEB-INF/classes
Please note that:
- This will disable caching for all the other template types (email templates and such) as well, so this is highly recommended to reenable caching after you return to production mode.
- This configures Velocity to load resources from the file system, instead of loading those from the class path. The reason is that caching can't be turned off for the class path based resource loader, probably due to a bug in Velocity. When you return to production mode, we suggest completely restoring your original configuration in velocity.properties.
After this you have to restart your Tomcat for the last time to pick up the changes in the Velocity configuration. After this you can edit your issue-fo.vm, reload your PDF and you will see the changes immediately!
Troubleshooting
Q: The PDF files are downloaded without any problem, but Adobe Reader cannot open them.
A: Your PDF files are corrupt, because there was an exception thrown during the rendering. This can be caused by syntax errors in the templates, for example. You should check your JIRA log first to find out the cause!
Q: The PDF files are downloaded without any problem, but Adobe Reader shows the File does not begin with '%PDF-'. error message when I try to open them.
A: Your PDF files are corrupt, because you forgot to install the JIRA patched class files. See again the Installation section above.
Q: I think I have some syntax errors in my issue-fo.vm template, but can't find out what. I would like to see the temporary FO document rendered from it, before that is translated to PDF.
A: You can turn on DEBUG logging by adding these lines to JIRA_HOME/atlassian-jira/WEB-INF/classes/log4j.properties and restarting JIRA. After that you will see the whole FO document in your JIRA log:
log4j.category.com.atlassian.jira.plugin.ext.pdfview = DEBUG, console, filelog
log4j.additivity.com.atlassian.jira.plugin.ext.pdfview = false
Comments (42)
Feb 18
Tibor Hegyi says:
Hi Ferenc, Thanks for the plugin, it works excellent! I especially like the PDF...Hi Ferenc,
Thanks for the plugin, it works excellent!
I especially like the PDF export of issue lists from the Issue Navigator.
Cheers,
Tibor
Feb 18
Ferenc Kiss says:
Glad you liked it, Tibor. We're not receiving too much feedback and honestly I d...Glad you liked it, Tibor. We're not receiving too much feedback and honestly I don't have the slightest idea why people are so uninterested in a solution for a highly popular issue...
Anyway, it's nice that some people confirm it working.
Feb 19
Inger Henning says:
I'd be very interested in this plugin\ however I cannot open your zip file to tr...I'd be very interested in this plugin- however I cannot open your zip file to try and install it- I get an error that states it's not a valid archive.
Feb 19
Ferenc Kiss says:
Strange you couldn't extract it, I tried it once again and there was no problem....Strange you couldn't extract it, I tried it once again and there was no problem. I packed the files to a RAR, download jira-pdfview-plugin-0.9-beta.rar from the attachments of this page and make a try again. Let me know whether it was OK (or you want to have this in some other archive format).
Ferenc
Feb 29
Igor V Demin says:
The is some problem, on each issue in appserver console shown two almost same WA...The is some problem, on each issue in app-server console shown two almost same WARNING:
"
2008-02-29 14:58:40,997 http-8080-Processor25 WARN [apache.fop.fo.FONode] Warnin
g(35/76): fo:table, table-layout="auto" is currently not supported by FOP
2008-02-29 14:58:40,997 http-8080-Processor25 WARN [apache.fop.fo.FONode] Warnin
g(83/76): fo:table, table-layout="auto" is currently not supported by FOP
"
I review plugin files but don't find something appropriate to change.
However, in the end of PDF-ing process I see the result.
Feb 29
Ferenc Kiss says:
Igor, Thank you very much for reporting this. The answer has been added to the F...Igor,
Thank you very much for reporting this. The answer has been added to the FAQ.
Feri
Mar 20
Litwin Sergey says:
Hi Ferenc. Could you explain how can I get custom fields from the Velocity conte...Hi Ferenc. Could you explain how can I get custom fields from the Velocity context?
Mar 20
Ferenc Kiss says:
At this moment, custom fields would be very difficult to access in .vm templates...At this moment, custom fields would be very difficult to access in .vm templates. If you need them supported, post a new feature request to our project JIRA. Thank you.
Feri
Apr 18
Ferenc Kiss says:
Hello Sergey. The brand new 0.9.1 version already comes with custom field suppor...Hello Sergey. The brand new 0.9.1 version already comes with custom field support, enjoy it.
Apr 18
Constantinos Coudounaris says:
I just download and installed latest version of PDF View. The PDF files ar...I just download and installed latest version of PDF View.
The PDF files are downloaded without any problem, but Adobe Reader shows "File does not begin with '%PDF-'" error message when I try to open them.
I await your reply.
Apr 19
Ferenc Kiss says:
Hello Constantinos. Would you be so kind to post a bug report, with the broken P...Hello Constantinos. Would you be so kind to post a bug report, with the broken PDF and your server log attached? (We suspect there is some exception thrown during generating the PDF.) Thank you for your cooperation.
Questions:
Apr 23
Jo-Anne says:
I have a similar problem where my pdf is not being displayed properly and in som...I have a similar problem where my pdf is not being displayed properly and in some cases actually crashing. I went back to double check that I had installed/configured everything correct and I discovered that I don't seem to have one of the files. Step 1 of the installation instructions says "Copy the plug-in JAR file jira-pdfexporter-plugin-xxx.jar to the JIRA_HOME/atlassian-jira/WEB-INF/lib directory. ". I don't seem to have a jira-pdfexporter... plugin. That may be my problem. Is it in the zip file and I just missed it. Or am I missing something else? Ideas?
Apr 23
Ferenc Kiss says:
Hello JoAnne, I'm sorry, it was a typo in the Step 1: the JAR name is {{jirapdfv...Hello Jo-Anne,
I'm sorry, it was a typo in the Step 1: the JAR name is jira-pdfview-plugin-xxx.jar (not jira-pdfexporter-plugin-xxx.jar), this is in the zip file and this should be copied to the lib directory. I fixed the installation instructions now.
If you still have the problem, then
Ferenc
Apr 23
Jo-Anne says:
Thanks for your quick response. I had wondered if it was a typo. &nb...Thanks for your quick response. I had wondered if it was a typo.
I have solved one problem, where the tags were not being interepted properly. I had a custom field of a "message" type. It was actually a field that I had forgotten was still on my test system (as I had decided not to put it in production). Anyhow, once I deleted that field everything is great for displaying a single issue in PDF format.
However. If I run a query and then try and export to pdf I get the follow dump (and I can send you the full output if you want).
Cause:
java.lang.Error: Unresolved compilation problems: The method getSearchRequestWithSearchSorts(Map, User) is undefined for the type SearchRequestManager The method getRequest(User, String) in the type SearchRequestManager is not applicable for the arguments (User, Long)
On this system I am running version 1.12. I am running a newer one in production 1.12.2 but I don't want to put this plugin there until I have confirmed that it is working.
I just checked all my other views (xml, word, excel) and they are also crashing. This seems strange to me as they were working. Would this plugin be responsible for these other problems? Or do I have bigger database issues that I need to investigate?
Apr 23
Ferenc Kiss says:
Or do I have bigger database issues that I need to investigate? No, this is a bu...Or do I have bigger database issues that I need to investigate?
No, this is a bug in our side
Reason is that the patched JIRA class files shipped with our plugin are not compatible with most recent JIRA version. We will try to provide a fixed version tomorrow or later this week. Please watch this page.
Apr 24
Ferenc Kiss says:
JoAnne! 0.9.2 just go released. This is to fix your problem with the search requ...Jo-Anne! 0.9.2 just go released. This is to fix your problem with the search request views. Please tell us whether it solves it.
Apr 24
Jo-Anne says:
Better....no crashing. I like that. However. If I run my filte...Better....no crashing. I like that. However. If I run my filter and then export my results to PDF. It displays the isues but the Priority is not getting set properly. It comes through as
Priority: $formatter.escapeXml($issue.prior
It is cut off on the right of my screen.
Interestly it seems to handle any of the priorities that came default with JIRA just fine (ie: medium). This error appear to be only for those issues that have one of our custom priorities (in this case: Show Stopper)
Apr 24
Ferenc Kiss says:
We've (re)tested it with a custom priority value and the PDF is exported without...We've (re)tested it with a custom priority value and the PDF is exported without any problem, and the custom value is there. Please file a bug report, attach the PDF and take a screenshot about your issue screen!
Can you see a Velocity exception stack trace in your JIRA log?
Apr 25
Jo-Anne says:
I believe that I have found the problem. I've submitted a ticket. Ba...I believe that I have found the problem. I've submitted a ticket. Basically though it appears that if an issue is unassigned, or if a field is not visable to a user then this error occurs.
Apr 25
Jo-Anne says:
I believe that I have found the problem. I've submitted a ticket. Ba...I believe that I have found the problem. I've submitted a ticket. Basically though it appears that if an issue is unassigned, or if a field is not visable to a user then this error occurs.
Apr 25
Ferenc Kiss says:
Thank you for the ticket. Solved it, see the fix here:Thank you for the ticket. Solved it, see the fix here: http://developer.atlassian.com/jira/browse/JPDF-1
Tell me if it helps you.
Apr 25
Jo-Anne says:
Looking good, working great. thanks for the quick response.Looking good, working great. thanks for the quick response.
Jun 05
Muhammad says:
I got following error when clicked on PDF icon. \\ Please help me. \\ \MR...I got following error when clicked on PDF icon.
Please help me.
-MR
[Fatal Error] :17:20: The reference to entity "T" must end with the ';' delimiter.
2008-06-05 13:54:05,733 http-443-Processor3 ERROR [ext.pdfview.renderer.IssuePdfRendererImpl] Failed to export
javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: The reference to entity "T" must end with the ';' delimiter.
at com.icl.saxon.IdentityTransformer.transform(IdentityTransformer.java:61)
at com.atlassian.jira.plugin.ext.pdfview.renderer.IssuePdfRendererImpl.renderFoToPdf(IssuePdfRendererImpl.java:115)
at com.atlassian.jira.plugin.ext.pdfview.renderer.IssuePdfRendererImpl.render(IssuePdfRendererImpl.java:69)
at com.atlassian.jira.plugin.ext.pdfview.view.PdfSearchRequestView.writeSearchResults(PdfSearchRequestView.java:77)
at com.atlassian.jira.plugin.searchrequestview.SearchRequestURLHandler.handleRequest(SearchRequestURLHandler.java:263)
at com.atlassian.jira.web.servlet.SearchRequestViewServlet.doGet(SearchRequestViewServlet.java:27)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:73)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:192)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.seraph.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:114)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:163)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132)
at com.atlassian.jira.web.filters.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:43)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.jira.web.filters.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:50)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.johnson.filters.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:89)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:39)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:165)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:139)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:198)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2460)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:119)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:157)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.xml.sax.SAXParseException: The reference to entity "T" must end with the ';' delimiter.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.icl.saxon.IdentityTransformer.transform(IdentityTransformer.java:59)
... 76 more
Jun 06
Ferenc Kiss says:
There is a syntax error in your .fovm template. If you attach it I can help you ...There is a syntax error in your .fo-vm template. If you attach it I can help you find it.
Jun 06
Muhammad says:
I just downloaded from the link provided,did not do any modification in any of&n...I just downloaded from the link provided,did not do any modification in any of .fo-vm template files (4 files).
Which one you reffered to?
Jun 06
Ferenc Kiss says:
If you didn't change anything then it must be some escaping problem. Does it hap...If you didn't change anything then it must be some escaping problem. Does it happen with all of your issues? (For example, when you create a single issue with summary='foo', can that be exported?). Can you upload a screen shot about one of your issues to reproduce it? I need to see the summary, description, comments, everything.
Jun 06
Muhammad says:
I can pull down details of a single issue in pdf without any problem.Like ...I can pull down details of a single issue in pdf without any problem.Like when I create a single issue with summary='foo', it can be exported.
But, whenever try to pull down all issues in current filter,it can not be exported, got the error.
Thank you.
-MR
Jun 07
Ferenc Kiss says:
Question: if there is a single issue that you can export without any problem, an...Question: if there is a single issue that you can export without any problem, and you set up your search that way that it returns that issue only (nothing else), then will the export of the search crash?
Jun 09
Muhammad says:
If I set up my search that way that it returns onely one issue (nothing el...If I set up my search that way that it returns onely one issue (nothing else), then the export of the search crashes.
-MR
Jun 09