In our Jira, system-user-nav-bar-sections.xml has been updated with the following:
<web-item key="view_core_help" name="View Core help" section="system.user.options/jira-help" weight="450">
<label key="jira.core.help" />
<tooltip key="jira.core.tooltip" />
<link linkId="view_core_help">/filelinks.jsp</link>
<param name="target" value="_blank"/>
<context-provider class="com.atlassian.jira.plugin.webfragment.contextproviders.HelpContextProvider" />
</web-item>
<web-item key="view_admin_help" name="View admin help" section="system.user.options/jira-help" weight="460">
<label key="jira.admin.help" />
<tooltip key="jira.admin.tooltip" />
<link linkId="view_admin_help">/filelinks.jsp</link>
<param name="target" value="_blank"/>
<context-provider class="com.atlassian.jira.plugin.webfragment.contextproviders.HelpContextProvider" />
<condition class="com.atlassian.jira.plugin.webfragment.conditions.IsAdminCondition"/>
</web-item>
The filelinks.jsp is very straight forward:
<%@ page import="com.atlassian.jira.component.ComponentAccessor" %>
<%@ taglib uri="webwork" prefix="ww" %>
<%@ taglib uri="webwork" prefix="ui" %>
<%@ taglib prefix="page" uri="sitemesh-page" %>
<html>
<head>
<title>JWST JIRA User Guides</title>
</head>
<body>
<page:capHide value="IFRAME">
<ui:soy moduleKey="'jira.webresources:soy-templates'" template="'JIRA.Templates.Headers.pageHeader'">
<ui:param name="'mainContent'">
<h1><a href="http://localhost:8080/JIRA-UG.pdf">JWST User Guide</a></h1>
<h1><a href="http://localhost:8080/JIRACORESERVER_8.7.pdf">JIRA Core Server Guide</a></h1>
<h1><a href="http://localhost:8080/ADMINJIRASERVER_8.7.pdf">JIRA Server Admin Guide</a></h1>
</ui:param>
</ui:soy>
</page:capHide>
</body>
</html>
We do this because our environment does not have access to the outside world.
In Jira 7.11, these PDFs open perfectly fine, but in Jira 8.4 they come out as garbage. Like the following:
I've looked at the web.xmls and Tomcat configs and can find nothing that is causing the PDF links to come out like this.
If you choose to download the file and then open it, it opens fine in the browser. So it appears to be something with the way the file is being hosted through Jira 8.4, and changed between 7.11.
Normally we run 8.4 with OpenJDK 11 but I switched it back to Java 8 just in case but that didn't change anything. I noticed the Tomcat versions are different but a very minor version change so I don't think it has anything to do with that.
Any help would be greatly appreciated!
UPDATE: So I have been able to host these PDFs successfully in different versions of Tomcat but still not through Jira 8.4 (or 8.7) so I overwrote the tomcat exes and jars in Jira's install with just the base version of Tomcat and now the 8.7 Core PDF displays fine but the Admin PDF and even just a test pdf with simply the word Test in it will not display, they come out with all the garbage. So what could possibly be installed with Jira 8.4/8.7 that would be causing this?
The funny thing is if I attach a PDF to an issue and click on it to be displayed, it opens fine, but I know Jira does it's own special magic with attachments.
I am assuming you are looking at JIRA Portfolio plugin. You can have many projects in one portfolio plan. But you can not see multiple portfolios in one view.
There is no way to see it in Confluence as of now. Hopefully there will be some gadgets for this soon and you can put it in Confluence.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.