1. Tempo Avatar Tempo
  2. Prime
  3. servertimesheet
  4. Issues

[TIME-82] Release for JIRA 4.1

Issue #82 resolved
Andriy Zhdanov created an issue

Hi there,

Could you please state when a JIRA 4.1 compatible version will be released?

Thanks,
Dirk

By dirk.lein/Dirk Lein on Thu, 22 Apr 2010 08:10:19 -0700

Comments (14)

  3. Andriy Zhdanov reporter

    Both reports are working in JIRA 4.1.
    Please select: Project page -> Summary -> Reports.

    By dariuszs on Mon, 3 May 2010 23:38:31 -0700

  4. Andriy Zhdanov reporter

    We have Jira 4.0.1 and the plugin is giving below error

    "Error loading gadget: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. HTTP error 500"

    Any updates on when we will get a compatible version ?

    By sandhya.kaithakkat on Mon, 7 Jun 2010 11:36:18 -0700

  6. Andriy Zhdanov reporter

    +1.
    Dariusz, can you please elaborate? Are you saying that this plugin is builtin into jira 4.1?

    By vladimir on Thu, 10 Jun 2010 23:25:48 -0700

  7. Andriy Zhdanov reporter

    Installed TimeSheet Report and Portlet v1.9 in Jira 4.1. Seems to work ok, but gives these warnings in the log:

    • timesheet report:
      /secure/ConfigureReport.jspa velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
    • Pivot report:
      /secure/ConfigureReport.jspa velocity org.apache.velocity.runtime.exception.ReferenceException: reference : template = templates/pivotreport/pivot-report.vm line 12,column 112 : $user.getName() is not a valid reference.

    By vladimir on Fri, 11 Jun 2010 01:16:06 -0700

  8. Andriy Zhdanov reporter

    We modified this plugin to make it work in 4.1, you basically need to strip the portlet part - something we don't need and created it as a new OSGi plugin. I'll try to convince our management to share our modified plugin.

    I've checked our logs again and we do get the same warnings as well, but the reports seem to work fine:

    /secure/ConfigureReport.jspa velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.

    By jo.voordeckers on Wed, 23 Jun 2010 02:37:34 -0700

  9. Andriy Zhdanov reporter

    Jo, please do not fork this plugin, you can submit your changes if you wish, or ask me instead.

    And please ignore this warning, or suppress it:

    Edit <JIRA_HOME>/WEB-INF/classes/log4j.properties, add the following lines mostly in the end, before THREAD LOCAL ERROR LOG APPENDER:

    log4j.category.velocity = ERROR, console, filelog
    log4j.additivity.category.velocity = false

    See also https://studio.plugins.atlassian.com/browse/TIME-37

    By azhdanov on Mon, 28 Jun 2010 07:14:31 -0700

  10. Andriy Zhdanov reporter

    Doesn't appear to be working for 4.1 standalone, Ubuntu Server 9.1.

    By kentr on Fri, 20 Aug 2010 10:37:01 -0700

  11. Andriy Zhdanov reporter

    Jo Voordeckers, if you're management would be willing to share the modified code with a nonprofit, I'd be grateful.

    If not, can someone give pointers on how to strip the portlet out? I know almost nothing about Java programming, so any clues would be very helpful.

    By kentr on Wed, 25 Aug 2010 10:50:55 -0700

  13. Andriy Zhdanov reporter

    Hi Andriy ,
    we've just upgraded to 4.4.3 using Plugin version: 2.2.3,and am seeing this again in the logs.
    will follow your log4j config , so it's just an fyi.
    BTW thanks for your xcellent plugin!

    By arthurpu on Wed, 30 Nov 2011 04:05:41 -0800

  15. Log in to comment
Assignee
Type
bug
Priority
major
Status
resolved
Component
–
Version
2.2.9
Votes
0
Watchers
1