nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I add a Jira issue Collector to a confluence page?

Paula Pokusa_iijq56

I created a jira issue collector in one of my jira projects. I want to embed that now in a confluence page that provides instructions for others to open issues for our team.

I have tried everything I could think of and I cannot get it to populate (we have cloud).

Is there a way to do this without looking at getting additional extensions or marketplace add ons?

Thanks!

Accepted answers

All comments

Fabian Lim

Hi @Paula Pokusa

By issue collector, are you referring for a form that creates jira tickets?

Thanks

Paula Pokusa_iijq56

Correct, followed the atlassian steps to create the issue collector here https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/ but now having a hard time utilizing the HTML code provided

Alex Koxaras -Relational-

Hi @Paula Pokusa

Interesting question you've got there, and I'm glad you asked! If I were a frontend developer perhaps I could give you a better solution than the one I've got here.

If I guessed right, you've done so far everything correct! And I know that the HTML code is giving you a hardtime, since it doesn't specify a height. The problem was that when I placed the collector inside the page, its height was so small, that I couldn;t see anything!

What I did, is to actually add a <div> on my code, and set a specific height for it e.g. 600 px. The good thing is that now it works:

issue collector open.png

The bad thing is that it creates to much blank space (see all the white space below the "provide feedback and above the blue highlighted space):

issue collector close.png

The HTML I used is:

<html>
<body>
<div>
YOUR SCRIPT HERE
</div>
</body>
</html>

And the CSS I used is:

div {
height: 600px;
}

Now, it's not the optimal solution, but it's the best I've got
Hope that helps a bit!

Paula Pokusa_iijq56

Interesting, I cannot even get it to display on my page. Are you just pasting it as plain text or using the code snippet macro?

I can see it generate using https://www.w3schools.com/cssref/tryit.asp?filename=trycss_display so I am at a loss for why it won't populate on my page.

Thanks for looking into this!

Alex Koxaras -Relational-

Do you have any macro about HTML, like Easy HTML?

Paula Pokusa_iijq56

Not currently. I did find a free app that allows the use of HTML and it seems like that is the best option. Interesting that it isn't a macro available to use, but thanks again for helping out!

Paula Pokusa_iijq56

Sorry to update my previous response, no it was not the form it was the issue collector. 2 different things, but surprisingly easy to confuse.

William Wilson

So. Let's just break this down. Again. Because, there's a dozen threads on this, and the same crap repeated.

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud

issue-collector