A pdf-export of a confluence page, containing JIRA issues using the JIRA-macro does not show images that are JIRA attachments.
During the pdf-export the JIRA access-log shows HTTP GET requests for the missing images with response code 302 (not found).
A application link between JIRA an Confluence is established using OAuth with impersonation in both directions.
Is this a configuration problem or a bug?
@michael_topic Can confirm, stopped working altogether.
Earlier versions seemed affected by the presence of a Table of Contents macro on the same page, but that no longer seems to be the case.
Please see and vote https://jira.atlassian.com/browse/CONFSERVER-39519
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not seeing the Jira application link ticket statuses in PDF exports of Confluence Product Requirements, where I have embedded the application link as a Jira object in a table cell. Sometimes I do, mostly I don't. I just see a raw URL to the ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make sure you have set correct server base url incase you are using context path in the server.
Read more here: https://confluence.atlassian.com/pages/editpage.action?pageId=148592
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Holger,
maybe this is your problem: https://jira.atlassian.com/browse/CONF-33020
There is a workaround for the problem, but the problem itself is not solved yet.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
CONF-33020 is not to the problem. The URL of the JIRA attached images is reachable. The problem is that but the Confluence PDF export request the JIRA attachments images without authentication.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm, I think, it is better to ask official Atlassian Support with that question (https://support.atlassian.com/help/). They can look at your logfiles and configurations and so on.
Maybe they know about this problem already.
Good Luck
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.