Query JIRA through Confluence (Applinks) REST API

[Ulrich Kuhnhardt]

Assume Confluence and JIRA are linked via applinks.

I'm looking for a solution to query JIRA through the Confluence (Applinks) REST API. Something like the {jira-issues] macro in confluence.

The JIRA issues macro on Confluence uses a proxy like http://localhost:1990/confluence/plugins/servlet/applinks/proxy and sends the query inside the request header (why??) as

1. X-AppId:
   59994da6-56a6-3e80-92b6-61f814f67399
2. X-AppPath:
   /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?

Is there a way to achieve the result directly?

https://answers.atlassian.com/questions/222396/applinks-in-javascript-get-project-keys-from-jira is a good start, but I need to get issue data.

[Anatoli]

Hi Uli,

https://docs.atlassian.com/jira/REST/latest/#d2e3178 will get your the list of issues with the fields.

Is there a way to achieve the result directly?

Do you mean directly contact JIRA from a browser and not proxy the requests? We have to proxy requests because the user's browser might not be logged into JIRA or the user might not have JIRA account at all and the applink is configured to use a different count.

[Ulrich Kuhnhardt [Comalatech]]

Hi Anatoli,

thanks for getting back on this one. I'm looking into the following scenario

<iframe> -> XDM (AP.request()) -> Confluence REST API --- Applinks ---> JIRA.

The jira-issues macro in Confluence does it like that (except for the iframe). I totally agree that the request from the browser should be proxied, but why is the JIRA query part of the request header? And not - as you would assume - part of the request query param?

Note that I don't want to talk to JIRA directly from the browser (because I'm a Confluence remote app plugin iframe).

[Anatoli]

Not sure why we pass it inside header.