[TIME-239] TimeSheet gadget was working with JIRA 4.2.4, but it doesn't work with JIRA 4.4.4

[Andriy Zhdanov]

TimeSheet gadget was working with JIRA 4.2.4, but now, it doesn't work with JIRA 4.4.

Error: "An internal server error occurred when requesting resource /rest/timesheet-gadget/1.0/timesheet.json"

We think it's a bug, because the correct url is /jira/rest/timesheet-gadget/1.0/timesheet.json and it works, but the gadget generates the wrong url /rest/timesheet-gadget/1.0/timesheet.json

There are serveral issues about this question, one of them is "https://studio.plugins.atlassian.com/browse/TIME-212", but it isn't resolved.

We have tried a workaround rewriting the url with Apache, but it doesn't work.

Would you be so kind, and help us with this issue?

Thank's in advance.

By juanlu/Juan Luis Serradilla on Mon, 26 Mar 2012 00:55:31 -0700

[Andriy Zhdanov]

Are you using right plugin verison, like 2.2.8?

By azhdanov on Mon, 26 Mar 2012 03:32:36 -0700

[Andriy Zhdanov]

Thank's for your interest on this issue, Andrew.

If you look at "Environment" field of this issue you will find the answer ...

By juanlu on Mon, 26 Mar 2012 03:47:14 -0700

[Andriy Zhdanov]

Sorry for not noticing it. Have you tried setting base url in jira options? See http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Options

By azhdanov on Mon, 26 Mar 2012 12:42:13 -0700

[Andriy Zhdanov]

Base url in JIRA is correct. If you look at https://jira.atica.um.es/jira/rest/gadgets/1.0/g/jira-timesheet-plugin:timesheet-gadget/gadget.xml, you will see the only wrong path seems to be the one I've reported in this issue (/rest/timesheet-gadget/1.0/timesheet.json), but the link https://jira.atica.um.es/jira/rest/timesheet-gadget/1.0/timesheet.json works ...

By juanlu on Tue, 27 Mar 2012 01:19:13 -0700

[Andriy Zhdanov]

We have tested it without ssl (http) and it works fine, but we need https, and it was working before migration (jira-4.2.4 + TimeSheet 2.1.0 with https), so it seems to be a bug, related with issue #212 "[TIME-212]", doesn't it? ...

By juanlu on Tue, 27 Mar 2012 04:01:03 -0700

[Andriy Zhdanov]

Hi Andrew,

We've resolved this issue by adding certificates to cacerts file in JIRA's JRE following JIRA documentation about configuring JIRA when it acts as client and it needs ssl. You plugin does just this (acts as a client and needs ssl), but we didn't know this issue, and it's the 1st time we have similar problem.

We have JIRA license and Atlassian support have helped us to resolve this issue.

You point to similar solution in issue #148 "[TIME-148] JIRA Timesheet Plugin GADGET doesn't support SSL?", linking to http://forums.atlassian.com/thread.jspa?messageID=257322616&#257322624

So, now we don't think there's a bug in your plugin, and we apologize for any inconvenience caused.

We really love your plugin and we ask Atlassian for including it in JIRA default installation on May-2011.

Thank's for your patience and you can close this issue.

By juanlu on Wed, 28 Mar 2012 00:56:54 -0700

[Andriy Zhdanov]

Great, thank you for your excellent feedback!

By azhdanov on Wed, 28 Mar 2012 11:17:46 -0700

[Andriy Zhdanov]

If any one else having similar problem and above did not help, please also check plugin version 2.2.9 (for Jira 4.4.x) with improvement issue #248 "[TIME-248] Group Timesheet with CAS Authentication" it may help.

By azhdanov on Sat, 14 Apr 2012 16:13:58 -0700