Generally, Atlassian does not support cross-product requests using their APIs (Atlassian Forge nor Connect) for third-party vendors. I found a technical approach to get this running for my apps, which worked for years. Now, Atlassian has changed AP.requests to restrict that in Confluence for "/wiki"-calls and actively prevent out-breaks: this stops the ability of my approach to retrieve data from Jira in Confluence Cloud! |
Pre-requisite: installed and active add-on "Group Sign-Off for Jira" on your Jira Cloud instance.
You often work with Jira but want to document your work within Confluence. But Confluence's native "Jira issues macro" cannot display anything other than the predefined fields: no group sign-off fields' properties at all. Therefore, use "Group Sign-Off for Jira inside Confluence" to solve this topic easily:
If you have configured many different Group Sign-Off fields, for example, representing different stages, etc., you may want to see them in a more compressed view: condensed Group Sign-Off fields are what you are looking for.
Add a new Group Sign-Off macro to your Confluence page and enable the option "condensed fields" (checkbox).
Now, you do not get a column per selected Group Sign-Off field, just a single column containing a bubble per selected Group Sign-Off field to display it's state being approved (green), declined (red), pending (yellow) , or n/a (white).
LIVE-Sample: display issues from my Jira-Cloud ...
If your configured JQL filter just retrieves a single issue, then no table header will be displayed and you get your configured field(s) only:
Otherwise, you'll get a table tree for your retrieved issues: