Is there a way to insert a JIRA Issue collector into Confluence Cloud?

[danny.marti]

I created an issue collector on my Jira project and was expecting to add it to my confluence page via HTML or java macro, but both seem to be unavailable in the cloud.

Is there any way to do this without having to buy an add-in?

[Diego · Accepted solution]

Hello there @danny.marti!

Currently, the only way to include a Jira Issue Collector in Confluence Cloud is by using a HTML Macro.

The HTML macro is not natively present on our Cloud platform for security reasons. There are, however, third-party options to this:

[Atlassian Marketplace] Confluence Cloud - HTML

You can check more details about the Jira Issue Issue Collector here:

• Use the issue collector
• Customize the Jira issue collector

Let us hear from you!

[Nelson Abbey]

cloud integration between JIRA and COnfluence is terrible frankly, really disappointed

[Marcel Kleinlütke]

the issue collector is a great piece of possibilities... I am asking myself what we can do to use it in the case of secured enviroments... Webpage in the www has a collector on it and the JIRA is in a company network without possibilies beside vpn to open from outside that network....

[LCD]

It's a bit weird that the two Atlassian products don't integrate better. Am I wrong? I almost expected there to be a macro specifically for Jira Issue Collector in confluence...

[ShawnS]

I'm really not wanting to pay for an HTML Macro app just to integrate something that Atlassian should be providing.  I really need to have an issue collector in one of my internal Confluence pages.

[Ashley Sainsbury]

Completely agree with the lack of integration between Jira and Confluence.  This seems like an easy win

[Chris Klein]

Its sad to me its easier to embed an issue collector on a google site than it is on one of Atlassian's own products. Wow...

[mweeks]

Is there a "feature" request somewhere in your backlog we can all go and upvote to make this addition.  Seems a HUGE oversight to have built this Issue Collector Option - but not let it be integrated natively into the tools meant to collaborate. 

[mweeks]

Upvote the issue here: https://jira.atlassian.com/browse/JRACLOUD-36918?filter=98703&jql=project%20%3D%20JRACLOUD%20AND%20summary%20~%20%22issue%20collector%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

[LCD]

Thank you mweeks. Voted. Mobile users please note that in order to see the "vote" link on the issue, you will need to have your browser render the page in desktop mode.

[Nelson Abbey]

Worklfow should really start with "Kicking the Can Down the Road Mate"

[William Wilson]

Good lord almighty in the heaven's above!

So. Let's just break this down.

Atlassian makes Jira.

Atlassian makes Confluence. 

I can embed a Jira issue or filter into Confluence, no problem.

I can embed an issue collector elsewhere in the world easily, with NO REGARD for security.

I can not embed an issue collector into a Confluence page, which is a side by side sibling product. Part of a suit of products, all marketed to "work together".

Why? Because it requires it to be wrapped in an HTML macro... which is insecure. HOWEVER... And oddly enough... if you want to pay for a third party add-on, the security concern magically vanishes!

And... this is where it gets annoying.

I can use "forms" (if the project is a work management project) to embed a "form" that collects issues in a confluence page... 

The FORM is not insecure enough to cause Atlassian to hamstring it!!!

Embedded Jira issues are not insecure!

But... They say the COLLECTOR *IS* insecure. Because, it must be wrapped in an HTML macro. HOWEVER... AGAIN... Using "Forms" is fine!!! AND... if you PAY for an add-on, no worries! Use the collector ALL YOU LIKE!

AS LONG AS YOU SPEND THOSE SWEET SWEET MARKETPLACE BUCKS!

Friends. This is gaslighting at it's finest. This is also what happens when Atlassian collects revenue from the add-on marketplace AND it's core product. 

All internal work to add value to the product grinds to a halt, because it is not generating ADDED revenue as part of the core product. It is only by pushing simple things like this off to the marketplace that they will generate ADDITIONAL revenue above and beyond the now over-priced core products that continue to see features dropped in favor of the marketplace add-ons. As is evidenced here.

The evidence shows repeatedly that, as Atlassian customers, our voices mean nothing to Atlassian as a company.

It's time to start looking elsewhere when doing our roadmap planning.