Kaamelot (Comment Archived 2008.01.15)

Added by Vincent Thoulé, last edited by Vincent Thoulé on Jan 15, 2008  (view change)
Do not delete this page.
As initial page of Kaamelot, it contains :
  • Its Change History
  • Its Comment History

Labels

plugin plugin Delete
codegeist codegeist Delete
worklog worklog Delete
report report Delete
jira jira Delete
portlet portlet Delete
transition transition Delete
dwr dwr Delete
upgrade upgrade Delete
settings settings Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (218)

 

  1. Aug 08, 2006

    Jimmy Wan says:

    Can this be used with JIRA 3.5.x? I want to use this and the GANTT plugin, but t...

    Can this be used with JIRA 3.5.x? I want to use this and the GANTT plugin, but that plugin appears to be incompatible with 3.6.x at this time.

    1. Aug 09, 2006

      Vincent Thoulé says:

      Jimmy, You can try with the 0.2.3

      Jimmy,

      You can try with the 0.2.3, I used it with JIRA 3.5.3.

      I will make some test with Kaamelot 0.2.5 against JIRA 3.5.x.

      Rgds
      Vincent

    2. Aug 11, 2006

      Vincent Thoulé says:

      Hi Jimmy, I have made some test against JIRA 3.5.3,but without success. Fastwor...

      Hi Jimmy,

      I have made some test against JIRA 3.5.3,but without success.
      Fastworklog plugin required AddOn plugin which used some new JIRA Component provided by :

      • atlassian-cache-servlet-0.5.5 provided in JIRA since 3.6.x (It was able to add it in 3.5.3)
      • atlassian-velocity-0.3.19, but JIRA 3.5.3 uses the 0.3.17 (with different effect with other components)

      To use it with 3.5.3 would require some developpement ... currently, I am in holiday !

      Perhaps in September
      Vincent

  2. Jan 11, 2007

    Dharmendra Varma says:

    When I added this plugins in my test environment, I see the enter a new wor...

    When I added this plugins in my test environment, I see the enter a new worklog link in the issue itself.  Attached please find the screen shot for the same.

    1. Jan 11, 2007

      Vincent Thoulé says:

      It is right. It is new foncitonnality that I prepared, but it is not yet validat...

      It is right.
      It is new foncitonnality that I prepared, but it is not yet validated.
      In the next SNAPSHOT (the finalized release is not yet finished), I will able to disable it.

      Vincent

      1. Jan 18, 2007

        Dharmendra Varma says:

        Hello Vincent, Let me first thank you for all work you have been doing.  Th...

        Hello Vincent,

        Let me first thank you for all work you have been doing.  This functionality is so useful.  Do you have any idea when the final version can be expected?

        Dharmendra

      2. Jan 30, 2007

        Dharmendra Varma says:

        Hello Vincent, Can you please let me know when to expect the final build as I ca...

        Hello Vincent,

        Can you please let me know when to expect the final build as I cannot use 3.7 till this is finalized.

        Dharmendra

        1. Jan 30, 2007

          Wojciech Seliga says:

          Hi Vincent, Our teams also is blocked with upgrade to JIRA 3.7.x without your pl...

          Hi Vincent,

          Our teams also is blocked with upgrade to JIRA 3.7.x without your plugin being released (without temporary things present in SNAPSHOT).

          Many thanks Vincent for this great plugin anyway.

          We are looking forward to the release. 

          Regards,

          Wojtek 

          1. Jan 30, 2007

            Vincent Thoulé says:

            Hi Dharmendra, Wojtek, As you can follow on

            Hi Dharmendra, Wojtek,

            As you can follow on http://developer.atlassian.com/jira/browse/KAAM-28 :

            • KAAM-31 would be surely reported of future release
            • KAAM-32 has been finished yesterday night,
            • KAAM-33 should be for the final release 3.7-1.0

            I am able to provide a new SNAPSHOT, but the installation procedure has be to strongly updated ...

            What are the minimum wanted functionnalities to be not blocked in your upgrade to JIRA 3.7 ?

            Rgds
            Vincent

            1. Jan 31, 2007

              Wojciech Seliga says:

              Vincent, For me, to upgrade to JIRA 3.7.x would be enough to have stable version...

              Vincent,

              For me, to upgrade to JIRA 3.7.x would be enough to have stable version (no temporary icons, messages, etc. ) of Kaamelot working with JIRA 3.7.x with the same functionalities like in Kaamelot 0.2.9. I appreciate new features (KAAM-28), but we could wait a little longer  for these features till you fully finish them. For now, we would like to finally upgrade to new JIRA 3.7.x features but having also your great plugin on board.

              Regards,

              Wojtek 

              1. Jan 31, 2007

                Vincent Thoulé says:

                Wojtek (and others) Are you able to have a look on yesterday night SNAPSHOT rel...

                Wojtek (and others)

                Are you able to have a look on yesterday night SNAPSHOT release ?
                This last one may be a candidate release. I will probably report other functionnalities.

                Rgds
                Vincent

                1. Jan 31, 2007

                  Dharmendra Varma says:

                  Hello Vincent, I could not find the latest snapshot for the download and test.&n...

                  Hello Vincent,

                  I could not find the latest snapshot for the download and test.  We were interested in entering the worklog and editing the worklog as it is a very major taks for us.  We use this time to bill our clients for T&M projects.

                  Dharmendra

                  1. Jan 31, 2007

                    Vincent Thoulé says:

                    Hi Dharmendra, Download area is mentionned in Overview section (

                    Hi Dharmendra,

                    Download area is mentionned in Overview section (http://kaamelot.fr.free.fr/build/), but the index.html page generate dynamically the displayed page (by javascript) and, sadely, failed with IE6.0. It seems to be available only with FireFox.

                    Download URLs are :
                    http://kaamelot.fr.free.fr/build/3.7-1.0/jira-plugin-kaamelot-addon-3.7-1.0-SNAPSHOT.jar
                    http://kaamelot.fr.free.fr/build/3.7-1.0/jira-plugin-kaamelot-fastworklog-3.7-1.0-SNAPSHOT.jar
                    http://kaamelot.fr.free.fr/build/3.7-1.0/jira-plugin-kaamelot-reporter-3.7-1.0-SNAPSHOT.jar
                    http://kaamelot.fr.free.fr/build/3.7-1.0/jira-plugin-kaamelot-myrddin-3.7-1.0-SNAPSHOT.jar

                    Vincent

                2. Feb 02, 2007

                  Wojciech Seliga says:

                  Hi Vincent, I have just checked the most recent Kaamelot SNAPSHOTs with newest ...

                  Hi Vincent,

                  I have just checked the most recent Kaamelot SNAPSHOT-s with newest JIRA 3.7.3.

                  It is still not satisfactory to finally migrate to JIRA 3.7.x as I found two problems.

                  1. a critical one: I cannot log work from fast worklog portlet for some projects - in my case I can do it for 3 projects, whereas I cannot do it for 1 project. I recieve "You don't have permissions to log work issues in this project". Of course I do have permissions and I can log work using normal way (from view issue screen) without any problems. The stack trace is:

                  INFO: Exec[0]: FastLogWorkAjaxUtil.addWorklogForPortlet()
                  java.lang.Exception: You do not have permission to log work on issues in this project.
                  at com.atlassian.jira.web.action.issue.FastLogWorkAjaxUtil.addWorklog(FastLogWorkAjaxUtil.java:206)
                  at com.atlassian.jira.web.action.issue.FastLogWorkAjaxUtil.addWorklogForPortlet(FastLogWorkAjaxUtil.java:228)
                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                  at java.lang.reflect.Method.invoke(Method.java:585)
                  at uk.ltd.getahead.dwr.impl.ExecuteQuery.execute(ExecuteQuery.java:239)
                  at uk.ltd.getahead.dwr.impl.DefaultExecProcessor.handle(DefaultExecProcessor.java:48)
                  at uk.ltd.getahead.dwr.impl.DefaultProcessor.handle(DefaultProcessor.java:83)
                  at uk.ltd.getahead.dwr.AbstractDWRServlet.doPost(AbstractDWRServlet.java:162)
                  at com.atlassian.jira.servlet.DWRServlet.doPost(DWRServlet.java:90)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
                  at com.atlassian.plugin.descriptors.servlet.ServletModuleContainerServlet.service(ServletModuleContainerServlet.java:38)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
                  ...

                  Strange... Any ideas

                  2. a simple on: when there is no worklog type defined for worklogs (that is for all worklogs before newest plugin has been installed - it means for all of them initially ), in the screen where I can edit all worklogs for given issue, I see Velocity code ($action.getWorklogTypeObject($worklog.worklogTypeId).nameTranslation) instead of something more reasonable like "empty", "undefined" or "n/a". I think you should address that.

                  I can report this problems using in bug tracking system for Kaamelot if you want. I did not do that just because it is still snapshot...

                  When could you adress these problems?

                  Thanks in advance,

                  Wojtek

                  P.S. I have fixed a few bugs in installation description of Kaamelot.

                  1. Feb 02, 2007

                    Vincent Thoulé says:

                    Thanks for fixing documentation bugs. Concerning your two problems : 1) The Fas...

                    Thanks for fixing documentation bugs.

                    Concerning your two problems :
                    1) The FastLogWorkAjaxUtil.addWorklog() method apply two verifications :

                    • 1st : That you have the WORK_ISSUE Permission, as it is done in standard
                    • 2nd : That the current Workflow State is workable. Functionnality implemented in Fastworklog since release 0.2.5 in 2006 August. See 4.Kaamelot FastWorklog#WorklogEdition.

                    As you can see, if you do not have given a value to "IsWorkable.Worflow.MetaAttribute" parameter, it assumes as value the JiraWorkflow.JIRA_META_ATTRIBUTE_EDIT_ALLOWED constant ("jira.issue.editable").
                    You should have, for 3rd projet, make the test on an issue which implements the MetaAttribute jira.issue.editable.

                    2) Yes, you are right. I have planned to fix it in the WE. It is possible create at least one WorklogType to for exemple "Undefined".

                    Vincent

                    1. Feb 02, 2007

                      Wojciech Seliga says:

                      Vincent, Thanks a lot for your explanation. Honestly I missed this change in 0.2...

                      Vincent,

                      Thanks a lot for your explanation. Honestly I missed this change in 0.2.5 - now I see - I tried to report time to closed issues (not editable) . Strangely no of my JIRA customers did not report this problem... It can be a little bit misleading that default behaviour of fastworklog differs to standard JIRA work log functionality (where you can log your work even for closed tickets). Why did you decide to make it different?

                      2) Any recommendation for a quick solution? Or should I wait for the official release?

                      Thanks in advance,

                      Wojtek 

                      1. Feb 02, 2007

                        Vincent Thoulé says:

                        Vincent, I made the difference in order to reply to requirements issued from my...

                        Vincent,

                        I made the difference in order to reply to requirements issued from my company.

                        • No Worklog is authorised on closed issues.
                        • Old Worklog (previous month) have not be updated after a few day of current month (5 days in our cases)

                        Note that I planned to implement Worklog Authorisation depending on Worklog Type.
                        The final reason is to be able to modify Original Estimate Time while a specified WorklogType has not been applied.
                        For exemple, we would be able to enter Worklog on an issue during Analysis and have always the ability to modify the Original Estimate Time.
                        Since another Worklog Type is used, then only Estimate Time may be is modified.

                        2) No special receommandation at the moment for a quick solution.
                        You create a Worklog Type as you want : "Undefined", "Unspecified", "n/a", "-".
                        I will probably implement a boolean option to (de)activate the WorklogType management ?

                        V.

                        1. Feb 02, 2007

                          Wojciech Seliga says:

                          OK now I understand. I think it makes sense to allow deactivating WorklogType ma...

                          OK - now I understand.

                          I think it makes sense to allow deactivating WorklogType management for given JIRA installation. Ideally without WorklogType enabled, Kaamelot should not require modification of entities configuration.

                          And I think that Kaamelot should not impose too much bureaucracy (I mean various worklog types + permissions for them). I like it how it is - lightweight

                          Is this restriction of inability to update old worklogs (older than X days) currently implemented? If yes, how can I configure it? 

                          Concerning the quick solution: I was asking how to get rid of this velocity statements in the table. I believe some changes in source code will be necessary...

                          Wojtek 

                          1. Feb 02, 2007

                            Vincent Thoulé says:

                            Desactivate the Worklog Type by using a Parameter should be easy to implement, b...

                            Desactivate the Worklog Type by using a Parameter should be easy to implement, but avoid Entities ugrade is not so easy !

                            Restriction of inability to update old worklogs is currently implemented, but not well documented ! It is mentionned in
                            FastWorklog Comment.

                            As quick solution in VM files for Worklog Editor, you may unpack Fastworklog, correct (as below) and repack it.
                            In secure\issue\views\WorklogDetails.vm

                            • Macro GetUpdatableWorkLogDetail
                              Replace 
                              <td><a href=$editAction>$action.getWorklogTypeObject($worklog.worklogTypeId).nameTranslation</a></td>

                              by 

                              <td><a href=$editAction>
   #if ($action.getWorklogTypeObject($worklog.worklogTypeId))
      $action.getWorklogTypeObject($worklog.worklogTypeId).nameTranslation
   #else
      None
   #endif
   </a></td>

                            • Macro GetUnupdatableWorkLogDetail
                              Replace 
                              <td>$action.getWorklogTypeObject($worklog.worklogTypeId).nameTranslation</td>

                              by 
                              <td>
   #if ($action.getWorklogTypeObject($worklog.worklogTypeId))
      $action.getWorklogTypeObject($worklog.worklogTypeId).nameTranslation
   #else
      None
   #endif
   </td>

                            Not tested !

                            V.

                            1. Feb 03, 2007

                              Vincent Thoulé says:

                              Hi, It will be best with #if ($worklog.worklogTypeId && $action.getWorklogT...

                              Hi,

                              It will be best with 

                              #if ($worklog.worklogTypeId && $action.getWorklogTypeObject($worklog.worklogTypeId))
      $action.getWorklogTypeObject($worklog.worklogTypeId).nameTranslation
   #else
      None
   #end

                              V.

  3. Jan 15, 2007

    ccyumi2008 says:

    Kaamelot AddOn UpgradeManager&nbsp;is not available. please check it. thanks.

    Kaamelot AddOn - UpgradeManager is not available.

    please check it. thanks.

    1. Jan 26, 2007

      Vincent Thoulé says:

      See Kaamelot AddOn UpgradeManager Documentation. Vincent

      See Kaamelot AddOn - UpgradeManager Documentation.

      Vincent

  4. Jan 29, 2007

    seb says:

    Hi Vincent, Thanks for your great plugin. I'm using the snapshot version because...

    Hi Vincent,

    Thanks for your great plugin. I'm using the snapshot version because I'm running JIRA 3.7 .

    Could you have a look at the following picture and tell me what am I doing wrong please ?


    Thanks,

    Seb. 

    1. Jan 30, 2007

      Vincent Thoulé says:

      Nothing ... It is a SNAPSHOT and its is new Panel, not yet finished, neither in ...

      Nothing ...
      It is a SNAPSHOT and its is new Panel, not yet finished, neither in current development.
      I planned to add a new Panel offering a new way to display worklogs in agreement with new features of Kaamelot (see http://developer.atlassian.com/jira/browse/KAAM-28).

      Bonne Journée

  5. Feb 01, 2007

    David Derumier says:

    I try to install FastWorkLog plugin, and I receive this error (JIRA 3.7.2): 2007...

    I try to install FastWorkLog plug-in, and I receive this error (JIRA 3.7.2):

    2007-02-01 18:15:58,281 Thread-1 ERROR [ContainerBase.[Catalina].[localhost].[/]] Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) com.atlassian.jira.upgrade.ConsistencyLauncher
    org.picocontainer.defaults.UnsatisfiableDependenciesException: com.atlassian.jira.issue.workers.DefaultWorkerManager doesn't have any satisfiable constructors. Unsatisfiable dependencies: [[interface com.atlassian.core.ofbiz.association.AssociationManager, interface com.atlassian.jira.issue.IssueManager, interface com.atlassian.jira.workflow.WorkflowManager, class com.atlassian.jira.issue.worklog.WorklogHelper]]
        at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.getGreediestSatisifableConstructor(ConstructorInjectionComponentAdapter.java:138)
        at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:193)
        at org.picocontainer.defaults.InstantiatingComponentAdapter.getComponentInstance(InstantiatingComponentAdapter.java:48)
        at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
        at org.picocontainer.defaults.SynchronizedComponentAdapter.getComponentInstance(SynchronizedComponentAdapter.java:35)
        at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
        at com.atlassian.jira.config.component.ProfilingComponentAdapter.getComponentInstance(ProfilingComponentAdapter.java:27)
        at org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfType(DefaultPicoContainer.java:274)
        at org.picocontainer.defaults.DefaultPicoContainer.getComponentInstances(DefaultPicoContainer.java:266)
        at com.atlassian.jira.ComponentManager.eagerlyInstantiate(ComponentManager.java:428)
        at com.atlassian.jira.ComponentManager.start(ComponentManager.java:327)
        at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:31)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
        at org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
    2007-02-01 18:15:58,359 Thread-1 DEBUG [org.objectweb.jotm.jta] Current.getStatus()
    2007-02-01 18:15:58,375 Thread-1 INFO [org.quartz.core.QuartzScheduler] Scheduler JiraQuartzScheduler_$_NON_CLUSTERED started.
    01-févr.-2007 18:15:58 org.apache.catalina.core.StandardContext start
    GRAVE: Error listenerStart
    01-févr.-2007 18:15:58 org.apache.catalina.core.StandardContext start
    GRAVE: Erreur de démarrage du contexte [] suite aux erreurs précédentes

    I checked installation, and all seems to be correct. Any idea?

    1. Feb 01, 2007

      Vincent Thoulé says:

      Yes, I have an idea. Picocontainer is not able to satisfy the dependencies of De...

      Yes, I have an idea. Picocontainer is not able to satisfy the dependencies of DefaultWorkerManager.

      • DefaultWorkerManager is provided by Kaamelot FastWorklog,
      • WorklogHelper is provided by Kaamelot AddOn

      1st : Did you install the two corresponding jars ?
      2nd : No trace in Library directory of old Kaamelot jars ?
      3rd : The plugin has been tested only against 3.7, not against 3.7.1 nor 3.7.2 !

      • WorklogHelper extends DefautlWorklogManager and implements WorklogManager. Perhaps, some method parameters have chnaged since 3.7.

      Let me know if the problem is resolved.
      I will try to test it against 3.7.3 (available since today).

      1. Feb 01, 2007

        Vincent Thoulé says:

        I made the test with a standalone release 3.7.3 without a such error. I will giv...

        I made the test with a standalone release 3.7.3 without a such error.
        I will give a preference to the 1st cause.

        A new release have been provided to correct missing declaration in entitygroup.xml required by Kaamelot Reporter.

        Vincent

  6. Feb 05, 2007

    ccyumi2008 says:

    Hi Vincent, I'm using Addon and Fastworklog 3.71.0 Shapshot&nbsp; in&nbsp; JIRA ...

    Hi Vincent,
    I'm using Addon and Fastworklog 3.7-1.0 Shapshot  in  JIRA 3.7.1 . I configured the  Portlet for a Fast Work Log (Based on Filter on my dashboard. There is a bug here:

    I only add time and worklog in one Issue, but the time and worklog is added to others issuesthe worklogs.  please find the attachement named worklog.bmp.

    1. Feb 05, 2007

      Vincent Thoulé says:

      Hi ccyuni2008, Due to security settings, I am not able to see from office, bitm...

      Hi ccyuni2008,

      Due to security settings, I am not able to see from office, bitmap file (Unable to render embedded object: File (?##$%) not found.).

      The bugs you mentionned was present in the first SNAPSHOT (9 January).

      Do you use the last SNAPSHOT (from Yesterday) ?

      Please, give preference to png or jgp images.

      Rgds
      Vincent

  7. Feb 05, 2007

    ccyumi2008 says:

    Hi,Vincent I download the latest version SNAPSHOT today. but my dashboard config...

    Hi,Vincent

    I download the latest version SNAPSHOT today. but my dashboard configured worlog occurred error as following. Can you help to check it why. thanks very much!

    -------------------- 

    An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- java.lang.NullPointerException at com.atlassian.jira.config.DefaultExtendedConstantsManager.initWorklogTypes(DefaultExtendedConstantsManager.java:96) at com.atlassian.jira.config.DefaultExtendedConstantsManager.getWorklogTypeObjects(DefaultExtendedConstantsManager.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.velocity.runtime.parser.node.PropertyExecutor.execute(PropertyExecutor.java:111) at org.apache.velocity.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:302) at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:157) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:131) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.runtime.directive.Parse.render(Parse.java:181) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:70) 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.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:60) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:55) at com.atlassian.jira.plugin.JiraResourcedModuleDescriptor.getHtml(JiraResourcedModuleDescriptor.java:90) at com.atlassian.jira.portal.PortletImpl.getViewHtml(PortletImpl.java:69) at com.atlassian.jira.portal.portlets.AbstractRequiresUserPortlet.getViewHtml(AbstractRequiresUserPortlet.java:25) at com.atlassian.jira.web.portlet.bean.PortletRenderer.getNormalHtml(PortletRenderer.java:83) at com.atlassian.jira.web.portlet.bean.PortletRenderer.renderPortlet(PortletRenderer.java:61) at org.apache.jsp.secure.views.dashboard_jsp._jspService(dashboard_jsp.java:1271) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) 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:279) 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:181) 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.JIRAProfilingFilter.doFilter(JIRAProfilingFilter.java:16) 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:41) 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.RequestCleanupFilter.doFilter(RequestCleanupFilter.java:49) 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 com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcerFilter.doFilter(DatabaseCompatibilityEnforcerFilter.java:25) 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.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) 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