[TIME-113] Gadget does not display information

[Andriy Zhdanov]

The timesheet gadget has been added to our system dashboard. JIRA is exposed internally through jira.local and externally through issues.domain.com. While accessing JIRA through jira.local (internal to the office) we are able to see content in the timesheet gadget. If we access JIRA through the external link (issues.domain.com) the timesheet gadget display _MSG_gadget.timesheet.title_ as the title and there is no content.

By cafletch/Colin Fletcher on Wed, 29 Sep 2010 08:01:32 -0700

[Andriy Zhdanov]

You probably faced a problem described in http://confluence.atlassian.com/display/JIRAKB/Gadgets+do+not+display+correctly+after+upgrade+to+JIRA+4.0

By pniewiadomski on Wed, 29 Sep 2010 13:46:45 -0700

[Andriy Zhdanov]

Hi,
I have the same issue with JIRA 4.1.2 standalone installed as a windows service.
It is setup as described on the atlassian documentation.
JIRA in running with Tomcat on port 8080.
We browse our dns on port 80 redirected by IIS to tomcat with the isapi_redirect.dll as described on the atlassian documentation.
I tried to add proxyName="MyDNS" proxyPort="80" in the server.xml file.
It makes me able to view the plugin correctly displayed on dashbord only when I browse it locally on the server using http://localhost.
When I try the same from my desktop using "MyDNS", the timesheet gadget displays "MSG_gadget.timesheet.title" as the title and there is no content.
Any help would be great!

By mixulup on Fri, 3 Dec 2010 09:01:59 -0800

[Andriy Zhdanov]

Just add a comment to tell you that I made a typo when writing the IP of my web site in the hosts file of my server.
So, the server was unable to call himself and to get the plugin spec.
It also explain why I could not browse it locally with "MyDNS" but it worked fine using localhost.
I wish I had check it earlier!

By mixulup on Mon, 6 Dec 2010 00:22:28 -0800

[Andriy Zhdanov]

I faced the same problem too. May I know got any solutions?

By huimian80 on Tue, 28 Dec 2010 00:18:00 -0800

[Andriy Zhdanov]

I am also having the same issue, is anyone currently working on this?

By bfagan on Tue, 28 Dec 2010 07:05:54 -0800

[Andriy Zhdanov]

Our host was using multiple names, one for internal, one for external which were not the same. If you change the name of your host to be (eg. issues.acme.com), use DNS views to resolve the address different for internal and external users... Then change the hostname to (ef issues.acme.com) the plugin will work.

This boils down to most of us likely using an alias that is different than the hostname. It would be good to tackle this and maybe use a properties entry so we are not forced to change the names of our server.

By cafletch on Tue, 28 Dec 2010 09:04:40 -0800

[Andriy Zhdanov]

Hi Colin, sorry that I can't really get what you mean, can you explain more on how should we do? Thanks.

By huimian80 on Tue, 28 Dec 2010 18:04:38 -0800

[Andriy Zhdanov]

Ok, so for this discussion lets assume:

hostname of the machine hosting jira (and the plugin) is centos.acme.local

The installer thought it would be a good idea to alias the machine for users to access the centos box to 'jira.acme.local'.

For external access, users are able to go to issues.acme.com.

Notice the different names? hostname: centos.acme.local, alias: jira.acme.local, external: issues.acme.com

If you access jira through centos.acme.local, the plugin will work. The others will not. The problem is the mechanism to 'get the hostname'

If you change the hostname from centos.acme.local to issues.acme.com, then only the external users will be able to see the plugin, unless you use dns views.

dns views allow you to provide a different ip address (name resolution) based on a whole bunch of different factors, one of which is where you are coming from. So by changing the hostname to issues.acme.com, and setting up dns views you can achieve happiness.

eg. dns views
(internal to the office) issues.acme.com -> resolves to internal ip.
(on a vpn) issues.acme.com -> resolves to vpn access address
(external) issues.acme.com -> resolves to external access point

By cafletch on Tue, 28 Dec 2010 20:55:42 -0800

[Andriy Zhdanov]

Hi Colin, finally we solved the problem. Thanks a lot for your useful information.

By huimian80 on Tue, 28 Dec 2010 23:39:33 -0800