4.Kaamelot FastWorklog

Added by Vincent Thoulé, last edited by Vincent Thoulé on Feb 14, 2007  (view change)

Description/Features

Kaamelot Fast Worklog provides differents plugin modules around Timetracking and Worklog...

  • A Component for WorkerManager (inspired of WatchManager)
  • A Portlet for Fast Worklogs
    • (See KAAM-1, KAAM-9, KAAM-11, KAAM-12, KAAM-13 and KAAM-17 )
    • Since 0.2.5, the Portlet is using DWR AJAX Framework
    • Since 0.2.8, the Portlet has been splitted in two distinct Portlet : One based on Worklog and the other on Request.
  • A Page Editor for Worklogs (inspired of editworklog.jsp) See JRA-2411
  • Workflow Function for WorkerManager (Start and Stop Working)

Usages

Fast Worklog Portlets

Configuration Screens

At configuration step, you have to specify :

  • For Portlet based on Worklog :
    • The retention delay is used to build a list of "Working On Issue" based on the last entered worklog.
    • Worklog History to specify retention delay is used to build a list of "Worklog" for each issue (Not yet managed, and defaultly set to 1).
    • The low time used for low worklog
    • The high time used for the high worklog
    • Sort parameters
  • For Portlet based on Request :
    • Filter
    • Filter restriction (forced to -1)
    • If Filter Description will be shown
    • Worklog History to specify retention delay is used to build a list of "Worklog" for each issue (Not yet managed, and defaultly set to 1).
    • The low time used for low worklog
    • The high time used for the high worklog
    • Sort parameters

Worklog Edition

  • FastWorLog Portlet through IWorkerManager.isWorkable(issue) assumed that an issue is workable until a predefined Worflow MetaAttribut do unauthorize it.
  • This predefined Worflow MetaAttribut is defaultly set to JiraWorkflow.JIRA_META_ATTRIBUTE_EDIT_ALLOWED (jira.issue.editable).
    Then, if at a Workflow step, Issue is not editable, it will not too workable.
    The wanted MetaAttribut may be modified by setting the applicationProperties "IsWorkable.Worflow.MetaAttribute" to new value.
  • For example, you may set the applicationProperties "IsWorkable.Worflow.MetaAttribute" to "jira.issue.workable".
    Also, you may specify in workflow steps, the MetaAttribut "jira.issue.workable" to True or to False.

It may be implemented later by Atlassian ?

Porlet in Dashboard

  • Click on Refresh Icon , the Working On Issues List is updated using Retention Delay.
  • You can add a new Issue in your Working On Issue List entering its key in top input.
  • On each listed Issues :
    • Click on Edit Icon to access the small Worklog editor (Full Javascript) ... See below.
    • Click on Details Icon , all personnal today's worklog will be shown.
    • Click on Remove Icon remove issue from Working On Issue List (Not available for On Request Portlet)
    • Click on TimeSpent value to access to the Worklog Editor (HTML/Velocity Page)
  • On each listed Worklogs :
    • You are able to see the Worklog Type.
    • Click on Edit Icon to access the small Worklog editor (Full Javascript) ... See below.
    • Click on Low Add Icon , to add a new Worklog (or update last one), with the Low Time specified in Configuration screen.
    • Click on High Add Icon , to add a new Worklog (or update last one), with the High Time specified in Configuration screen.
    • Click on TimeSpent value to access to the Worklog Editor (HTML/Velocity Page), the specified Worklog ready for update.

Worklog Editor Dialog Box

  • Click on ? Icon , to read About PopUp.
  • Click on x Icon , to close the Worklog editor.
  • Time, Comment and Comment Level are available for edition.
    See KAAM-11 : Comment Level and Worklog Type are not available under I !E
I am always looking for a simple DHTML ComboBox

Worklog CustomFieldType and CustomFieldSearcher

Inspired from J.Nolen's Vote and Watcher Plugin.
These modules dive the ability to see the list of Worker on an issue.

Version History

Ver. JIRA Contents Author
0.1.0   Initial Release Vincent Thoulé
0.2.0   New Features Vincent Thoulé
0.2.1   New Kaamelot Release Vincent Thoulé
0.2.3   Bug Fixing and Maven 2 / Continuum integration Vincent Thoulé
0.2.5   Enhancement and DWR integration Vincent Thoulé
0.2.6   Enhancement and bug fixing Vincent Thoulé
0.2.7   Enhancement, bug fixing and uses of overrided DWRSerlvet Vincent Thoulé
0.2.8   Enhancement, New Portlet based on Saved Filters Vincent Thoulé
0.2.9   Bug Fixing : Allow use of Portlet in Default Dashboard Vincent Thoulé
3.6-1.0 3.6.x Bug fix (same as 0.3.0-SNAPSHOT) Vincent Thoulé
3.7-1.0 3.7.x Migration to JIRA 3.7 + KAAM-32 Vincent Thoulé
3.7-1.1-SNAPSHOT 3.7.x Fix KAAM-58 Vincent Thoulé

Labels

plugin plugin Delete
codegeist codegeist Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (124)

 

  1. Mar 06, 2006

    Bettina Zucker says:

    Hello Vincent,  I missed something. How do you get to the configuration ste...

    Hello Vincent,
     I missed something. How do you get to the configuration step?
     I cannot see anything new in my Jira after installation of your portlet.
     Maybe it is because I don't know where to look for!

     Cheers

     Bettina Zucker 

    1. Mar 06, 2006

      Vincent Thoulé says:

      The configuration step is available when you add the Portlet in the Dashboard co...

      The configuration step is available when you add the Portlet in the Dashboard configuration (Manage Portal in english, Gérer Portail in French).

      Can you too verify if Plugin is enabled in Administration Screen menu System\Plugin ?

      Let me know, if you encounter any problem.

      Rdgs
      Vincent

  2. Mar 06, 2006

    Bettina Zucker says:

    Hello Vincent, thank you very much, now I understood how it works\! The plugin w...

    Hello Vincent,

    thank you very much, now I understood how it works! The plugin was enabled in the Administration Screen. I added the portlet to my Dashboard and could configure it and then I could find the portlet in my dashboard.

    Some small problems left: I cannot see the icons + , ++ , pen, and x . When I try to edit my worklogs I always get the message "Modification out of date, reserved only for Project Managers !" independently of the time of the worklog (I'm using the JAWorkLogListener.class of Jes Alring to be able to set worklogs for the past, it works well together with your tool). So I could not edit any of the worklogs with your Issue Worklog Editor, don't know why.

    But the fast worklog works well and is very nice! I'll surely install it into my productive system after some more testing.

    Cheers!

    Bettina 

    1. Mar 06, 2006

      Vincent Thoulé says:

      Concerning the icons, I am aware about this, and I will produce a corrected rele...

      Concerning the icons, I am aware about this, and I will produce a corrected release as soon as I will have currently resolve some trouble with my environment (WTP 1.0, SVN and Apache configuration).

      Concerning the "Out Of Date Modification" message, it is a function implemented to avoid to edit validated worklogs.

      In our implementation, developpers are not authorized to correct their worklog over a date calculated as follow : Previous month and older worklogs can not be edited after the begin of current month plus a number of day. This number of day is defaultly set to 3 days.
      It may be modified through by adding a JIRA application parameter in PROPERTYENTRY and PROPERTYSTRING tables :
      Worklog.Update.Delay.In.Days = x where x is number if day.
      or through the code :

      ApplicationProperties appProperties = ManagerFactory.getApplicationProperties();
appProperties.setString(WORKLOG_UPDATE_DELAY_DAYS, "10");

      I know that this parameter have to be available in the User Interface by administrators for modification, in a nearly future.

      1. Mar 07, 2006

        Bettina Zucker says:

        Hello Vincent, I cannot edit any of the worklogs with your editor, even if I jus...

        Hello Vincent,

        I cannot edit any of the worklogs with your editor, even if I just created them (see html code below).
        Do I need some special permission? How are Project Managers defined? What else could be missing?

        Cheers

        Bettina

        <html><head></head><body>
        <h2>Issue Worklog Editor</h2>
        <form>Issue Key : <input name="key" value="RGIIISW-422" />
        </form>

        <form>
        <h4>Worklogs entered for
        <a href="/browse/RGIIISW-422" >RGIIISW-422</a></h4>
        <br>
        <table border="1" cellpadding="5">
        <tr>
        <th>Developper</th>
        <th>Entered on</th>
        <th>Spent time</th>
        <th>Comment</th>
        </tr>

        <tr><td>bettina</td>
        <td>2006-03-07 11:00:18.161</td>
        <td>1 Stunde</td>
        <td></td>
        </tr>
        <tr><td colspan=4 border=0>
        <i><font color=red face='Verdana, Arial, Helvetica, sans-serif' size=1 >
        Modification out of date, reserved only for Project Managers !
        </font></i>
        </td></tr>

        </table>
        <p>
        </form>
        </body></html> 

        1. Mar 07, 2006

          Vincent Thoulé says:

          A new release will be shortly provided a set of corrections. Vincent

          A new release will be shortly provided a set of corrections.
          Vincent

  3. Mar 09, 2006

    Aggelos T. Paraskevopoulos says:

    Salut Vincent, latest version (0.2) of the plugin that we tried seems to work fi...

    Salut Vincent,

    latest version (0.2) of the plugin that we tried seems to work fine. Very nice work. I just wanted to know if there is a way to modify the description (comment) of a worklog that was accidently entered without one. It seems that the edit screen for modifying worklogs that you provide cannot generate the appropriate link to enable this on an empty comment. I suspect that this would be a common error during adoption of the plugin, so it would be nice to have this too.

    A.

    1. Mar 11, 2006

      Vincent Thoulé says:

      Aggelos, In case of no comment, you should see a href link with "No Comment" in...

      Aggelos,

      In case of no comment, you should see a href link with "No Comment" in red and italic. I encounter the same problem with home installation with Tomcat, but no problem at the office with Websphere.
      I don't think it is due to Server. I think more that it is i18n problem... I investigate.

      Rgds
      Vincent

    2. Mar 12, 2006

      Vincent Thoulé says:

      Concerning comment modification (when it had not been entered previously) it dep...

      Concerning comment modification (when it had not been entered previously) it depends which SGBD you are using...
      At office, I use Oracle with BLOB for long string, and if no comment is entered a null was stored and my Worklog Editor evaluate correctly if the comment is set to NULL.
      At home, using HSQL, I encounter the same problem than your's, because no comment entered create an empty string.

      I will correct this in nest release, with other evolutions.
      Rgds
      Vincent

  4. Mar 16, 2006

    Vincent Thoulé says:

    Bettina, I made a quick correction jirapluginkaamelotfastworklog0.2.2.jar

    Bettina,

    I made a quick correction jira-plugin-kaamelot-fastworklog-0.2.2.jar .
    Let me know, if you encounter other problem.

  5. Mar 16, 2006

    Bettina Zucker says:

    Hello Vincent, the problem has disappeared with version 0.2.2. It would be helpf...

    Hello Vincent,

    the problem has disappeared with version 0.2.2.
    It would be helpful to have the correct plugin version number in the Current Plugins overview while doing such tests though!
    It's the number taken from the atlassian-plugin.xml file, tag <version>, I think.

    Cheers

    Bettina 

    1. Mar 18, 2006

      Vincent Thoulé says:

      Bettina, I have corrected the Plugin version to 0.2.2, but it is always not syn...

      Bettina,

      I have corrected the Plugin version to 0.2.2, but it is always not synchronised with Jar version (0.2.3), due to Maven 2 Integration. It will be repaired in next release.

      Rdgs
      Vincent

  6. Apr 13, 2006

    Matt Kenigson says:

    Never mind.&nbsp; I realized I hadn't yet put the required addon jar in place......

    Never mind.  I realized I hadn't yet put the required addon jar in place.  I also found out that if you disable this plugin and restart with it disabled when you enable it something happens to the iterator (gives a warning about a null value) and none of your portlets show up in the AddPortlet page.  Turning it off fixes that but the real fix was to turn it back on, stop and restart jira.

  7. Apr 14, 2006

    Matt Kenigson says:

    First, let me tell you how much I appreciate this plugin.&nbsp; Great work\! I'm...

    First, let me tell you how much I appreciate this plugin.  Great work!

    I'm seeing some errors in the log:

    2006-04-13 16:07:06,841 WARN [velocity] Warning! The iterative  is an Iterator in the #foreach() loop at [0,0] in template templates/timesheetportlet/timesheet-portlet.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
    2006-04-13 16:07:06,908 ERROR [velocity] RHS of #set statement is null. Contextwill not be modified. templates/plugins/portlets/issuesummaryfastworklog.vm [line 23, column 1]
    2006-04-13 16:07:06,909 ERROR [velocity] ASTMethod.execute() : exception invoking method 'getPrettyDuration' in class com.atlassian.jira.issue.helper.WorklogHelper : java.lang.IllegalArgumentException: java.lang.ClassCastException@5a5519
    2006-04-13 16:07:06,910 ERROR [velocity] RHS of #set statement is null. Contextwill not be modified. templates/plugins/portlets/issuesummaryfastworklog.vm [line 26, column 1]

    I know you've already addressed the warning as trivial.  I just included it because it really clutters up the logs and  that's annoying.  Is there an easy way to turn down the logging or supress this particular warning?  I hate things in the log that I can't do anything about.

    What do you think about the errors? 

    1. Apr 14, 2006

      Vincent Thoulé says:

      Hi Matt, Concerning the first error Warning! The iterative is an Iterator in th...

      Hi Matt,

      Concerning the first error Warning! The iterative is an Iterator in the #foreach() loop at [0,0], it is trivial, and I do not find how to suppress it, without recoding the Portlet.
      Concerning the second one : java.lang.ClassCastException, I will make some search to idenitify it (and perhaps resolv it).
      Rgds
      Vincent.

  8. Apr 18, 2006

    Matt Kenigson says:

    Jonathan, &nbsp;Any chance we can get some issue tracking attached to this fanta...

    Jonathan,

     Any chance we can get some issue tracking attached to this fantastic plugin?  Honestly, after using it for a few days I'd say it has changed my usage patters in JIRA for the better more than any other extension, bar none.  I anticipate it will get quite popular and will need its own JIRA space.

    Vincent, I have a small improvement suggestion:  It would be great if you could have more than one worklog per issue displayed in the portlet at a time.  Here's a use case:  I'm working on issue FOO-207 and have added it to the portlet.  I enter a short description and add some time to the worklog via the plus buttons.  Later in the day, I do some work on that issue that has nothing to do with the comment I entered previously.  I have two choices: 

    1) I can edit the description on my existing worklog and add time to it.  This has two big downsides.  First, if this happens a lot during the day, the description is going to get quite long, which is annoying.  More importantly, however, by avoiding the granularity of separate worklog entries you don't have a good idea of when things actually came up during the day, which can be problematic in certain situations.

    or

    2) I can  create another worklog.  Two issues with this, too:  First, the path to creating a new worklog is the link to the full worklog entry screen.  It's a whole lot better than having to go to the issue and then click on log work, but it breaks out of the whole fast-worklog interface.  Second issue is that the portlet will only display one (presumably the latest) worklog for a given issue, so now I can only add time to the second worklog and cannot easily add time to the first through the portlet.

    What I am suggesting is:

    1) Allow one to create another worklog simply by putting the issue key into the "work on an issue" text field.  Alternately you could change the behavior of the existing "enter a new worklog" button, although I can see the existing behavior as useful in some cases so you could add another button for adding a blank worklog for that issue.

    2)  This is implicit in the above suggestion:  Allow two or more worklogs from the same issue to be displayed at a time.  The portlet should display all of the worklogs for that day.  Everything else would essentially work the same way.  Only one blank worklog per issue should be available the following day, regardless of how many worklogs were displayed the previous day.

    Hopefully I will have some time I can devote in the future to contributing code to this wonderful plugin.  Great work, Vincent. 

    1. Aug 08, 2006

      Vincent Thoulé says:

      Hi Matt, If you do not have yet see it, please have a look on the last release ...

      Hi Matt,

      If you do not have yet see it, please have a look on the last release (0.2.5) of FastWorkLog plugin.

      Best
      Vincent

  9. Apr 19, 2006

    Vincent Thoulé says:

    Hi Matt, Your improvment suggestion are interesting too, and I have already som...

    Hi Matt,

    Your improvment suggestion are interesting too, and I have already some idea how to implement them.
    My plugins may/should be hosted in Altassian Developer Network for SVN and JIRA.
    I hope to provide these modification for the next release.

    Rgds
    Vincent

  10. Jun 12, 2006

    Vicki Alexander says:

    Hi, Vincent. I have recently downloaded JIRA 3.6.2 and also the three kaamelot p...

    Hi, Vincent.

    I have recently downloaded JIRA 3.6.2 and also the three kaamelot plug-ins.  When I try to use the portlet, I am not able to edit a worklog.  The path that shows in the explorer bar at the bottom left is: secure/issue/views/EditIssueWorkLog!default.jspa?key=SCR-455.  This is not a path available by default in 3.6.2.  Also, I am not able to find a jsp file named "EditIssueWorkLog" in any folder.  What am I missing here? Do I need to download the EditIssueWorkLog from somewhere and place it

    Vicki

    1. Jun 12, 2006

      Vincent Thoulé says:

      Hi Vicky, "EditIssueWorkLog" is not a JSP, but an action defined directly in th...

      Hi Vicky,

      "EditIssueWorkLog" is not a JSP, but an action defined directly in the plugin Jar, and served by a set of Velocity files.

      <!-- Work Log Editor -->
<action name="issue.EditIssueWorkLog" alias="EditIssueWorkLog">
	<view name="success">/secure/issue/views/EditIssueWorkLogs.vm</view>
	<view name="error">/secure/issue/views/EditIssueWorkLogs.vm</view>
	<view name="input">/secure/issue/views/EditIssueWorkLogs.vm</view>
	<command name="selectWorklog" alias="selectWorklog">
		<view name="success">/secure/issue/views/EditIssueWorkLogs.vm</view>
	</command>
	<command name="updateWorklog" alias="updateWorklog">
		<view name="success">/secure/issue/views/EditIssueWorkLogs.vm</view>
	</command>
</action>

      What kind of error message did you encountered ?

      Notice, that I am currently validating Kaamelot Plugins under JIRA 3.6.2 with new enhancement (KAAM-1).
      Rgds
      Vincent

      1. Jun 27, 2006

        Vicki Alexander says:

        It is a nullpointerexception error. &nbsp;An error occurred whilst rendering th...

        It is a nullpointerexception error.

         An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- java.lang.NullPointerException at org.apache.velocity.context.InternalContextAdapterImpl.get(InternalContextAdapterImpl.java:162) at org.apache.velocity.runtime.parser.node.ASTReference.getVariableValue(ASTReference.java:623) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:151) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:450) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:76) at com.atlassian.jira.plugin.webwork.JiraPluginWebworkVelocityServlet.service(JiraPluginWebworkVelocityServlet.java:50) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:253) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:51) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55) at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:182) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.LoginFilter.doFilter(LoginFilter.java:177) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132) at com.atlassian.jira.web.filters.ProfilingAndErrorFilter.doFilter(ProfilingAndErrorFilter.java:25) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.johnson.filters.JohnsonFilter.doFilter(JohnsonFilter.java:91) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.gzip.GzipFilter.doFilter(GzipFilter.java:72) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:534)

      2. Jun 27, 2006

        Vicki Alexander says:

        I searched the harddrive for all \.vm files and did not find the EditIssueWorkLo...

        I searched the harddrive for all *.vm files and did not find the EditIssueWorkLogs.vm that is mentioned above.  Shound this view file be on my harddrive for this to work. 

        Sorry for my ignorance. I am just beginning understand how all the different pieces work together.

        1. Jun 27, 2006

          Vincent Thoulé says:

          Hi Vicky, The EditIssueWorkLogs.vm file is provided by the archive jirapluginka...

          Hi Vicky,

          The EditIssueWorkLogs.vm file is provided by the archive jira-plugin-kaamelot-fastworklog-0.2.3.jar at secure\issue\views path.

          Note that jira-plugin-kaamelot-addon-0.2.3.jar is too required in your lib path.

          What is your UseCase to encounter this error ?
          What is your technical environment (SGBD, OS, ...) ?

          Rgds
          Vincent.

          1. Jun 28, 2006

            Vicki Alexander says:

            Thanks for the explanation....

            Thanks for the explanation.  I opened the jar file and understand more now

             Use Case

            1. Create a the Working On Issues Portlet
            2. Add Work (10 minutes) to an issue so that Issue # and the work total shows in the portlet
            3. Click the work Total (10 minutes)
            4. Error Occurs

            Technical Environment

            Windows Windows Server 2003 Enterprise Edition running in a VMWare

            Oracle 92

             JIRA 3.6.2 standalone

          2. Jun 28, 2006

            Vicki Alexander says:

            jirapluginkaamelotaddon0.2.3.jar is in my lib path Vicki

            jira-plugin-kaamelot-addon-0.2.3.jar is in my lib path

            Vicki

            1. Jun 28, 2006

              Vincent Thoulé says:

              Vicki, I tried to reproduce the NullPointerException with your usecase, but I s...

              Vicki,

              I tried to reproduce the NullPointerException with your usecase, but I succed only to produce a RuntimeException.

              With this release,
              1. The Timetracking have to be activated
              2. Any user with worklog permission is able to enter a Worklog from the Portlet
              3. Only Project Manager and Assignee are able to Edit Worklogs

              Let me know, if its helps you.

              Rgds.
              Vincent

              1. Jun 30, 2006

                Vicki Alexander says:

                Hi Vincent, Thanks for your help on this. I have&nbsp;checked the following: 1) ...

                Hi Vincent,

                Thanks for your help on this.

                I have checked the following:

                1) Time Tracking is currently ON.

                2) I have the permission "Work on Issues".  

                3)  I am the assignee.  I also am the one that added the original work that I am editing.  I amable to use the other functions of the portlet without error.

                I am still having the issue.  Today, I will download the jars again, and restart JIRA. 

                Please let me know if you can think of anything else.

                Thanks,

                Vicki

              2. Jul 28, 2006

                Ruk says:

                3. Only Project Manager and Assignee are able to Edit Worklogs I used Jira 3.6....

                3. Only Project Manager and Assignee are able to Edit Worklogs

                I used Jira 3.6.1, plugin version 0.2.5.

                Any user can modify any work log. Why?

                BR, Ruk 

                1. Jul 29, 2006

                  Vincent Thoulé says:

                  Hi Ruk Oups, You are right ! I have just made a correction. Please, let me a re...

                  Hi Ruk

                  Oups, You are right ! I have just made a correction.
                  Please, let me a return about it.

                  Vincent

          3. Jun 30, 2006

            Vicki Alexander says:

            Vincent, The Use Case is to place the portlet for a Fast Work Log on the dashboa...

            Vincent,

            The Use Case is to place the portlet for a Fast Work Log on the dashboard.  Add work to an issue so that the time (10 min) shows in the portlet.  Click on the time link (10 min).  The error occurs

            I am not sure what SGBD is.

            My environment is:  JIRA 362 standalone Enterprise using Oracle 92.  Windows Server 2003, JMV 1.4.  The browser in IE.

            Thanks,

            Vicki

  11. Jun 12, 2006

    Alistair Hopkins says:

    Hi, Very impressed by the FastWorklog stuff makes Jira useful for timetracking\!...

    Hi,

    Very impressed by the FastWorklog stuff - makes Jira useful for timetracking!

    One request - if I wanted to get a timesheet report for a saved filter what would be the quickest way to realise it?

     This would enable all sorts of really useful things - we group issues using various custom fields (eg cost basis) and being able to report on time spent by these custom fields would be transformational.  We laready make a filter for each custom field option...

     Thanks,

    Alistair 

    1. Jun 27, 2006

      Vincent Thoulé says:

      Hi Alistair, Concerning TimeSheet plugin report, the release provided by Kaamel...

      Hi Alistair,

      Concerning TimeSheet plugin report, the release provided by Kaamelot will not be more continue.

      Andrew Zhdanov has already reproduce my enhancement in his original plugin Timesheet report and portlet, and future request will be managed in it.

      I will study your proposal after having provided the next Kaamelot release (AddOn and FastWorklog only).

      Rgds
      Vincent