[TIME-176] Jira Timesheet version 2.2 for Jira version 4.4 not loading

[Andriy Zhdanov]

Jira Timesheet plugin doesn't load when adding to the dashboard:
We are using Jira Version 4.4.
I installed the time sheet plugin version 2.2 from this url:
https://studio.plugins.atlassian.com/svn/TIME/jars/jira-timesheet-plugin-2.2.jar

According to this URL: https://studio.plugins.atlassian.com/wiki/display/TIME/JIRA+Timesheet+Plugin, Jira 4.4 uses plugin 2.2.

I put the plugin in the right directory /plugins/installed-plugins/
When i restart jira plugin is enabled and I can add to the dashboard but it will not load as you can see in the screenshot.

I am getting this warning on the logs:
http-8090-5 WARN dony.tandijono 77x2x1 1454636 127.0.0.1 /secure/Dashboard.jspa gadgets.embedded.internal.GadgetUrlBuilder GadgetUrlBuilder: could not parse spec at rest/gadget/1.0/legacy/spec/com.fdu.jira.plugin.timesheet:portlet.xml

Can you please help me identify the issue? we are running our Jira in Debian OS.
Thank you.

By dony.tandijono/Dony Tandijono on Sat, 17 Sep 2011 18:28:58 -0700

[Andriy Zhdanov]

Same problem for me, on a fresh install of Jira 4.4

By mabrothier on Thu, 22 Sep 2011 05:18:09 -0700

[Andriy Zhdanov]

Small add-on: when I access the page on the same network, it works fine. But behind the NAT (simple port forwarding), this plugin doesn't show anything.

By mabrothier on Thu, 22 Sep 2011 11:42:48 -0700

[Andriy Zhdanov]

Had similar issue, had to resolve it with putting firebug in FF or the Chrome dev console and check the request/response that was going on. At the end, I found out that the URL for my JIRA (e.g. http://machine:8080/) was not resolving properly through my DNS, which required http://machine.internal.company.com:8080/. I changed my web page to go to the latter address and everything worked ok. I did see through firebug though that the response had an issue with the DNS resolution of the server name, so look into that.

By ksymeon on Sat, 24 Sep 2011 01:51:57 -0700

[Andriy Zhdanov]

BTW, I've got v2.2 on JIRA 4.4 and 4.4.1 working ok.

By ksymeon on Sat, 24 Sep 2011 01:52:23 -0700

[Andriy Zhdanov]

Same problem here. Jira 4.4; Plugin 2.2
Even when opening the page containing the plugin locally on the Jira-Server, the plugin remains in loading state.
Also a DNS-problem can be excluded.

By basilea7 on Sat, 24 Sep 2011 15:15:19 -0700

[Andriy Zhdanov]

Same problem here with v4.4.1#660- r161644 and 2.2 of the Timesheet Plugin

By jamiegordon911 on Thu, 6 Oct 2011 15:44:51 -0700

[Andriy Zhdanov]

I can confirm this issue as well in versions 2.2.1, 2.2.2, and 2.3 (all under Jira 4.4). The issue for me almost certainly has to do with the URL I'm using to access the page. I am using SSL and have Jira listening on 8443 (the default). If I access Jira using https://server:8443, all is well. I have an iptables rule to NAT all 443 traffic to 8443, however, and despite everything else loading properly if I use https://server (which would be equivalent to https://server:443), the time sheet just "spins". The Base URL setting in Administration does not affect this behavior (i.e. regardless of if I use https://server:8443 or just https://server).

By jeremyrnelson on Mon, 10 Oct 2011 13:02:55 -0700

[Andriy Zhdanov]

I'm sorry I can't help with this issue, I feel like I should collect my own trouble shooting instructions, but for now please look at issue #148 "[TIME-148] JIRA Timesheet Plugin GADGET doesn't support SSL?" - "JIRA Timesheet Plugin GADGET doesn't support SSL" also. Then see also general troubleshooting page: http://confluence.atlassian.com/display/JIRAKB/JIRA+Dashboard+and+Gadgets+Troubleshooting

By azhdanov on Tue, 11 Oct 2011 06:51:53 -0700

[Andriy Zhdanov]

My problem was a missing netfilter to route outgoing traffic from port 80 to 8080 (and 443 to 8443 for SSL) (see issue #174 "[TIME-174] Timesheet Gadget does not find REST ressource"). Maybe you should check that.

By htietgens on Tue, 11 Oct 2011 07:03:11 -0700

[Andriy Zhdanov]

I had a similar problem to Henning where I had to create an output rule for localhost (127.0.1.1), since the base URL was resolving to localhost on the box itself. I had already redirected 443 to 8443 using a PREROUTING rule for any external connections, but the timesheet gadget REST apparently is made from within the app to itself. See this blog post for more info:

http://jeremyrnelson.tumblr.com/post/11571758506/using-iptables-to-redirect-port-443-to-8443

By jeremyrnelson on Mon, 17 Oct 2011 12:19:46 -0700