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; } } }

Why arent my Bamboo Gadgets displaying in Jira?

Dan Carter

I'm connecting the latest version of Jira (6.1) to the latest Version of Bamboo (5.2) and issue sharing, build display etc is working fine. However the gadgets for dashboards only display a blank box...

The jira server is running over https, bamboo is just straight http. I've tried with the Jira Bamboo plugin, manually subscribing (as per the confluence wiki). Pointing towards the CNAME address, the machine:port dns address and the ip:port address and get the same results every time Its not essential to our use of Jira, but it would be nice if all the features worked!

Any help greatly appreciated

Accepted answers

pschaff01

Hi Dan,

Have you already tried to bypass your JIRA's HTTPS access to verify if the problem continues (you can test this by accessing JIRA directly on the server via localhost:PORT)? Also, how is your application link between JIRA and Bamboo configured?

One possibility is to do the following:

Delete the existing application link
Create a new application link between JIRA and Bamboo but instead of the domain name try to use the IP:PORT of each application to configure the link (only if they are running in the same network)
If everything runs fine after the test above (which will bypass SSL, proxy configurations, etc.) you can keep the configuration like this (using IP:PORT) and then only modify the "Display Name" of the application link to use the actual domain name with SSL. By doing this, the applications will have a direct communication channel without SSL/proxy usage and anyone that needs to use the Application Link feature will only be able to use it through the domain URL.

If this doesn't help you, you can raise a support ticket with us in support.atlassian.com and we will be glad to troubleshoot this further with you!

Cheers!

All comments

pschaff01

Hi Dan,

One possibility is to do the following:

Delete the existing application link
Create a new application link between JIRA and Bamboo but instead of the domain name try to use the IP:PORT of each application to configure the link (only if they are running in the same network)
If everything runs fine after the test above (which will bypass SSL, proxy configurations, etc.) you can keep the configuration like this (using IP:PORT) and then only modify the "Display Name" of the application link to use the actual domain name with SSL. By doing this, the applications will have a direct communication channel without SSL/proxy usage and anyone that needs to use the Application Link feature will only be able to use it through the domain URL.

If this doesn't help you, you can raise a support ticket with us in support.atlassian.com and we will be glad to troubleshoot this further with you!

Cheers!

Dan Carter

Hi Pietro,

Thanks for getting back to me.

I've done as you've suggested and thats exactly how I got the application link to work in the first place. Literally everything else works fine and seemingly even the gadget subscription (if added manually) seems to setup ok, its just that when I try to view the gadgets, I just see a blank box. I think I may raise a support ticket if theres nothing else I can try.

Dan Carter

Ok, so in a complete fit of stupidity, I have found the problem. It turns out, google chrome was blocking the bamboo rest gadget urls. Because our installation of bamboo isnt running https (where as Jira is) it was blocking them because they were from an "insecure" source. So in fact, this has probably always been working, just didnt notice the little grey shield in the address bar in google chrome. Incidentally, firefox works perfectly without any issue.

testcore

So I ran into this on Firefox 26.0; enabling the insecure content fixed the gadgets. Although, what I find odd about that specifically is that the Fisheye gadgets, also from an insecure source, don't have this problem.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration