| Since 3.7-1.6, the Installation has been changed. See details on in Kaamelot Web Site. |
Dependencies
Among Kaamelot plugins, only jira-plugin-kaamelot-addon has no dependencies (except JIRA librairies).
The 3 others (Fastworklog, Myrddin and Reporter) have jira-plugin-kaamelot-addon in dependencies.
Installation
Depending on wanted features, you will have to :
- Copy the following Kaamelot Plugin Jars into JIRA librairies directory :
- jira-plugin-kaamelot-addon-3.7-x.y.jar
- jira-plugin-kaamelot-fastworklog-3.7-x.y.jar
- jira-plugin-kaamelot-myrddin-3.7-x.y.jar
- jira-plugin-kaamelot-reporter-3.7-x.y.jar
- jira-plugin-kaamelot-i18n-3.7-x.y.jar
- Extract JSP files into WebApp directory (jar xvf Jar_File JSP_Full_Path_Name)
- From jira-plugin-kaamelot-addon-3.7-x.y.jar
- secure/admin/views/worklogtypes/deleteworklogtype.jsp
- secure/admin/views/worklogtypes/editworklogtype.jsp
- secure/admin/views/worklogtypes/viewworklogtypes.jsp
- From jira-plugin-kaamelot-fastworklog-3.7-x.y.jar
- secure/views/issue/logtypedwork.jsp
- From jira-plugin-kaamelot-addon-3.7-x.y.jar
- Waiting for a way to extend OFBIZ definition through Atlassian Plugin, a set of XML configurations are included in jira-plugin-kaamelot-addon-3.7-x.y.jar
- entityengine.xml : it shows how to modify the original entity-model-reader in JIRA entityengine.xml.
- entitydefs/entitygroup.xml : it shows the entity-group to add in original JIRA entitygroup.xml.
- entitydefs/entitymodel.Kaamelot.AddOn.xml : entitymodel XML file to add in of Classes/entitydefs sub-directory.
You should take entitydefs/entitymodel.Kaamelot.AddOn.xml as it is and copy it to appropriate place (see below). From entityengine.xml and entitydefs/entitygroup.xml you should extract marked sections and put them into appropriate sections in original JIRA entityengine.xml and entitydefs/entitygroup.xml files.
- Append Worklogtype Icon definition in Classes/iconimages.properties
For example, You may append Icons embedded in FastWorklog.jar# Worklog Types icon.worklogtype.study=/download/resources/jira.plugin.kaamelot.fastworklog:fastWorklogManagment/icons/wlStudies_16.png icon.worklogtype.analisys=/download/resources/jira.plugin.kaamelot.fastworklog:fastWorklogManagment/icons/wlAnalisys_16.png icon.worklogtype.development=/download/resources/jira.plugin.kaamelot.fastworklog:fastWorklogManagment/icons/wlDevelopment_16.png
- For Report Features (WorkloadReport)
You will have to update Classes/velocity.properties declaring a new macro librairies : templates/reports/reporterMacros.vm as follow :# VELOCIMACRO PROPERTIES velocimacro.library = templates/email/macros.vm, templates/plugins/jira/macros.vm, templates/jira/issue/table/macros.vm, templates/reports/reporterMacros.vm
In case of Standalone JIRA, assumes
- JIRA librairies directory : atlassian-jira-enterprise-X.X.X-standalone/atlassian-jira/WEB-INF/lib
- WebApp directory : atlassian-jira-enterprise-X.X.X-standalone/atlassian-jira
- Classes/entitydefs : atlassian-jira-enterprise-X.X.X-standalone/atlassian-jira/WEB-INF/classes/entitydefs
In case of Buildable JIRA, assumes
- JIRA librairies directory : <jira_dist_home>/edit-webapp/WEB-INF/lib
- WebApp directory : <jira_dist_home>/edit-webapp
- Classes/entitydefs : <jira_dist_home>/edit-webapp/WEB-INF/classes/entitydefs
Database Impact
Due to mentionned Entity Model upgrade, new entities are availables :
| Entity Name | DB Table | Overview |
|---|---|---|
| WorklogType | worklogtype | New JIRA Constant to specify Worklog Types |
| Worklog | jiraworklog | Extend of Action entity assuming the qualification of original JIRA Worklog |
| View Entity Name | Overview |
|---|---|
| ViewWorklogAction | View on entities Worklog and Action for new Worklog Features |
| ViewExtendedWorklogAction | View on entities Action, Issue and NodeAssociation for Reporter Features |
| A new attribut is about to be introduced in the original JIRA LogWork action .. . To be follow ! |

Comments (32)
Feb 26, 2007
Dharmendra Varma says:
Vicent, I installed the plugin as explained. However, when I try to log wo...Vicent,
I installed the plugin as explained. However, when I try to log work using log work screen in the issue, I see worklog type field with a dropdown. There are no values in the dropdown. Am i missing something?
Feb 26, 2007
Vincent Thoulé says:
Yes, You have to define your own Worklog Type through the administration page a...Yes,
You have to define your own Worklog Type through the administration page as it is described in AddOn section ...
The Worklog Type Icon to enter in Classes/iconimages.properties are just required to have proposed icon in the Worklog Type Administration page.
V.
Feb 27, 2007
Dharmendra Varma says:
Thank Vincent When I am clicking on Worklog Types in Administratin, getting the ...Thank Vincent
When I am clicking on Worklog Types in Administratin, getting the error
HTTP Status 404 - /secure/admin/views/worklogtypes/viewworklogtypes.jsp
type Status report
message /secure/admin/views/worklogtypes/viewworklogtypes.jsp
description The requested resource (/secure/admin/views/worklogtypes/viewworklogtypes.jsp) is not available.
Apache Tomcat/5.5.20
I checked and the file viewworklogtypes.jsp is present in the directory /secure/admin/views/worklogtypes. There was no directory orginally worklogtypes, which I created manually.
Feb 27, 2007
Vincent Thoulé says:
Notes that the WebApp directpry change depending on the type of WebServer : the...Notes that the WebApp directpry change depending on the type of WebServer :
Follow the installation correctly.
V.
Jun 05, 2007
akasian says:
I've downloaded all plugin files fromI've downloaded all plugin files from http://cv.thoule.free.fr/kaamelot.fr/3.7-1.9/Installation/Download.html and began to install it...
According to installation instruction I've copied all JARs to JIRA librairies directory
But next step confused me:
"... Extract JSP files into WebApp directory
From jira-plugin-kaamelot-addon-3.7-x.y.jar
secure/admin/views/worklogtypes/deleteworklogtype.jsp
secure/admin/views/worklogtypes/editworklogtype.jsp
secure/admin/views/worklogtypes/viewworklogtypes.jsp ..."
because file downloaded by me (http://cv.thoule.free.fr/kaamelot.fr/build/3.7-1.9/jira-plugin-kaamelot-addon-3.7-1.9.jar) doesn't contain secure folder at all :0
Please, orient me in this question. Thanx
Jun 05, 2007
Vincent Thoulé says:
The installation documentation on Confluence Kaamelot Pages is not up to date. Y...The installation documentation on Confluence Kaamelot Pages is not up to date.
You have to follow the installation documentation from Kaamelot sites.
JSP file and XML configuration are provided by http://cv.thoule.free.fr/kaamelot.fr/build/3.7-1.9/jira-plugin-kaamelot-settings-3.7-1.9.jar.
Rgds
Jun 18, 2007
seb says:
Hi Vincent, I have the following error traces in tomcat after the plugin has be...Hi Vincent,
I have the following error traces in tomcat after the plugin has been installed :
Plus, when I try to enter a new worklog I get the following error message :
org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Worklog][worklogtype,][id,11657] (SQL Exception while executing the following:INSERT INTO jiraworklog (ID, WORKLOGTYPE) VALUES (?, ?) (ORA-01400: impossible d'insérer NULL dans ("JIRA"."JIRAWORKLOG"."WORKLOGTYPE") ))My configuration :
I had to return back to an older version of the plugin for thing to get working.
Have you any clue regarding these errors ?
Thanks,
Seb.
Jun 18, 2007
Vincent Thoulé says:
Hi Seb, Mentionned Velocity errors are known, but it appears that it does not h...Hi Seb,
Mentionned Velocity errors are known, but it appears that it does not have any impact on wanted behavior. I have to find them for next releases.
Concerning the GenericEntityException, can you give me more details on your settings :
Waiting theses details directly on http://developer.atlassian.com/jira/browse/KAAM .
Rgds
Vincent
Jul 26, 2007
Dmitry Beransky says:
Hey Vincent, I"ve followed the installation instructions for Jira 3.10. Go...Hey Vincent,
I"ve followed the installation instructions for Jira 3.10. Got everything in place: I can see Worklog Types screens in Admin (and I've added two worklog types), I can see the Time Spent tab in issue view. However, when I go into Log Work screen, it doesn't have the new fields (the date field and the drop down for types). However, when I enter time using the old screen, the entry does show up in the Time Spent tab, but it looks weird.
Any idea why the Log Work screen doesn't have the new fields? Did I miss anything during installation (I double checked a few times and seems I did everything that was listed)?
Thanks
D.
Jul 27, 2007
Vincent Thoulé says:
Hi Dmitry, With JIRA 3.10 and Kaamelot 3.101.12, there is only Worklog type fie...Hi Dmitry,
With JIRA 3.10 and Kaamelot 3.10-1.12, there is only Worklog type field added. Date field has been added since JIRA 3.10. These bith field was provided by Kaamelot 3.7-1.10 for JIRA 3.7.x/3.9.x.
To view the WorklogType field, you should :
What do mean by "weird" for Time Spent Tab ?
Note that Report Component used for Kaamelot Report and Kaamelot Time Spent Tab is using JIRA Category feature which only provided in JIRA Enterprise Edition.
Vincent
Jul 27, 2007
Dmitry Beransky says:
Vincent, I do have logtypedwork.jsp in the correct location: !sshot1.jpg! ...Vincent,
I do have logtypedwork.jsp in the correct location:
and I do have two worklog types defined:
here's what my log work screen looks like. As you see there are no Kaamelot related fields here:
and finally, here's the "weird" Time Spent field:
what do you make of this all?
Jul 28, 2007
Vincent Thoulé says:
Hi Dmitry, Problem identified ... Follow KAAM103Hi Dmitry,
Problem identified ... Follow KAAM-103
V.
Jul 29, 2007
Dmitry Beransky says:
Thanks\! So, there is currently no solution and when you have one, you'll ...Thanks!
So, there is currently no solution and when you have one, you'll add it to KAAM-103, did I understand that right?
Cheers
D.
Aug 01, 2007
Vincent Thoulé says:
Hi Dmitry You are right. The only short term solution is to way a new release. ...Hi Dmitry
You are right. The only short term solution is to way a new release.
I am currently in holiday, and have to restore a new dev. environment on my laptop.
V.
Aug 06, 2007
Dmitry Beransky says:
\\Aug 17, 2007
Tim Graffam says:
Im having a heck of a time getting this working. I believe Ive followed th...Im having a heck of a time getting this working. I believe Ive followed the necessary steps but the WorkLog screen hasnt changed. The only indicator something is different is I now have a "Time Spent" tab in the lower section of my Detail screen, however the only thing that shows up when selected is "#Report()". The only thing I want to use this plug-in for is the Worklog Types.
The installation instructions on the Maven site arent exactly the clearest in the world, so could someone please review the steps Ive take to see it theres anything I may have missed?
Running JIRA 3.9.3
- Kaamelot - View on Worklog with extended data -><entity-group group="default" entity="ViewWorklogAction"/>
<entity-group group="default" entity="ViewExtendedWorklogAction"/>
<!
- Kaamelot - Entity for Worklog Type -><entity-group group="default" entity="WorklogType"/>
<entity-group group="default" entity="Worklog"/>
Between the installation instructions provided on Mavens site, and the ones provided here (which according to the notice at the top of this page arent up-to-date), I cant see anything Im missing which would cause this not to work.
Any suggestions would be much appreciated!
Aug 17, 2007
Wojciech Seliga says:
Tim, Your installation story looks good with two small exceptions: you do not&nb...Tim,
Your installation story looks good with two small exceptions: you do not need jira-plugin-kaamelot-fastworklog-0.2.0.jar at all (everything is in core file) and you maybe forgot about modyfing velocity properties file (which is only needed for reports AFAIK).
My questions:
If I know the answers, maybe I will be able to help.
Regarding unclear installation instructions - I have to agree with you.
Vincent had to move documentation from this wiki to his own hosting system (and published as Maven site), which made various contributions for improving docs quality very cumbersome. Anyway I think that if you or anybody else would like to improve readability and consistency of this documentation, Vicent (who does not seem to be the strongest English speaker) will be more than happy - just contact him - he is very responsive.
Regards,
Wojtek
Aug 17, 2007
Tim Graffam says:
I removed the fastworklog.jar I also added the velocity.properties setting and t...I removed the fastworklog.jar
I also added the velocity.properties setting and this did seem to fix the Time Spent tab - it shows " No worklog entered".
One question I have is that I dont have a file "templates/reports/reporterMacros.vm" - in fact, I dont have a reports folder at all in the templates folder. I also searched the contents of all of the Kaamelot jar files and couldnt find it there either. Should this file exist someplace if Im specifying it here?
Wojtek, to answer your questions in the order you asked them:
There are two current issues I have right now:
The format of this is ' {2} ' (representing weeks, days, hours and minutes - where * can be any number) Examples: {3} and {4}. Note: Your current conversion rates are {5} = 5 and {6} = 8.Vincent- What do you mean by "failed in error when used with Non Categorized project"? What is considered a categorized project?
Im definitely making headway here and hope Im just missing a couple remaining steps. Im hoping once this is working like I think it should we will have the ability to select worklog types and then be able to display the total time time a user has spent on a particular worklog type for a specific issue.
Thanks for the quick response guys!!
Aug 17, 2007
Vincent Thoulé says:
Tim, Concerning the 2nd issue, it is directly link to the Non Categorised proje...Tim,
Concerning the 2nd issue, it is directly link to the Non Categorised projects. By this term, I think about Projects which have not been linked to a Category. The Category is a feature only provided by JIRA Enterprise Edition.
For Performance reasons (See http://developer.atlassian.com/jira/browse/KAAM-23), I do not use default APIs, but an OFBIZ view. The performance has been enhanced, but sadely, the side-effect is that only worklogs of projects linked to a Category are visibles.
In "Worklog" Tab, it is normal that you do not see Worklog Types (this tab has not be overriden
). For the "Time Spent" tab showing "No worklog entered", it is surely because your project does own to a Category.
Concerning the 1st issue, I have a small idea. I encountered a similar problem with JIRA 3.10 (See http://jira.atlassian.com/browse/JRA-13059); I will have to verify it on JIRA 3.9.x. But I do not assure you that it will be fixed for Kaamelot-3.7-X. Since JIRA 3.10, there are lot of change around Worklog, and the Kaamelot-3.10-X is not yet stable. I am working on a new release based on JIRA-3.10.1 ... But it take some time (I am in holiday !).
Rgds
Vincent
Aug 18, 2007
Wojciech Seliga says:
Tim, 3 I meant your web app server log file catalina.out for Tomat, atlassianjir...Tim,
3 - I meant your web app server log file - catalina.out for Tomat, atlassian-jira.log or whatever else you have configured.
It seems to me that your setup looks good. The last question: do you use Enterprise version of JIRA?
Wojtek
Aug 20, 2007
Tim Graffam says:
Its works\! Once I created the category and added the project to it, the Time Sp...Its works!
Once I created the category and added the project to it, the Time Spent filled in as expected.
Im still experiencing the 1st issue I mentioned however. Basically, what it looks like is that the numbers surrounded by brackets are variables or placeholders for the examples that should be provided. In other words this:
The format of this is ' {2} ' (representing weeks, days, hours and minutes - where * can be any number) Examples: {3} and {4}. Note: Your current conversion rates are {5} = 5 and {6} = 8.Should look like this:
The format of this is ' *w *d *h *m ' (representing weeks, days, hours and minutes - where * can be any number) Examples: 4d, 5h 30m, 60m and 3w. Note: Your current conversion rates are 1w = 5d and 1d = 8h.Youll notice that each of the "bracketted numbers" in the first example are replaced by their respective values in the second example.
Unfortunately we are not planning on upgrading to 3.10 any time soon so if you have any thoughts how how this can be fixed in the version I have let me know and Ill give it a shot. (For example would there be any files I can hardcode these values in?)
The only other problem Ive found is on the "Workload Reports". As you can see in the following screenshot the "Report Unit" appears to be in French. Is this a hard-coded value I can change someplace?

Finally, is it possible to filter a Worklog report by a particular issue field? Specifically, I would like to only display a Worklog report for a specific "Fix Version". The "Worklog Report (Issue) says that "Aggregation available on Issues attributes", but I don't see how to do this.
Thanks again for all your help on this guys and especially for your quick responses!
(And yes Wojtek - I am using Enterprise JIRA)
Aug 28, 2007
Vincent Thoulé says:
Hi Tim, Please follow opened issues KAAM105Hi Tim,
Please follow opened issues KAAM-105,KAAM-106,KAAM-107 concerning some of your questions.
Others questions answered by mail.
Rgds
Vincent
Aug 17, 2007
Vincent Thoulé says:
Tim, As Wojtek mentionned, jirapluginkaamelotfastworklog0.2.0.jar is not requir...Tim,
As Wojtek mentionned, jira-plugin-kaamelot-fastworklog-0.2.0.jar is not required for the installation.
Also, concerning all report features (Report, Timspent Panel), keep in mind that they failed in error when used with Non Categorised project (see http://developer.atlassian.com/jira/browse/KAAM-61).
Note that, as it is mentionned in (http://confluence.atlassian.com/display/JIRAEXT/Kaamelot), these current page is obsolete and no more updated. The documentation has been move to a Maven site for different reasons :
As Wojtek mentionned too, English is not my mother language, but I make my best !
If my installation is not the clearest, I am ready to enhance it.
Do not hesitate to contribute !
Let me know about any comment.
Vincent
Dec 11, 2007
ramesh says:
Hi, Can anyone pls tell me with this plug in can we make log workdone mandatory ...Hi,
Can anyone pls tell me with this plug in can we make log workdone mandatory at particular workflow transition
pls help me on this.
-ramesh
Dec 11, 2007
Vincent Thoulé says:
Hi Ramesh This features is available only since 3.101.x releases through Custom...Hi Ramesh
This features is available only since 3.10-1.x releases through Customfields
Rgds
V.
Dec 11, 2007
ramesh says:
we are using 3.7.2 version ,suggest me wat plugin jars are compatiable for 3.7.2...we are using 3.7.2 version ,suggest me wat plugin jars are compatiable for 3.7.2 version
and i have included 3.7-1.10.1 plugin jars , it is giving version not compataible error
Dec 11, 2007
Vincent Thoulé says:
As mentionned in pedigree sectionAs mentionned in pedigree section, for JIRA 3.7.x, the last up to date release is Kaamelot 3.7-1.10.1.
V.
Dec 11, 2007
ramesh says:
Thanks Vincent ....u mean to say the plugin is not compatable for 3.7.2 version ...Thanks Vincent ....u mean to say the plugin is not compatable for 3.7.2 version , am i right ? ..pls confirm ..
Dec 11, 2007
Vincent Thoulé says:
Kaamelot 3.71.10.1 is comptible with all JIRA 3.7.x to 3.9.x. V.Kaamelot 3.7-1.10.1 is comptible with all JIRA 3.7.x to 3.9.x.
V.
Dec 12, 2007
ramesh says:
Hi Vincent, 20071212 12:19:48,753 http8090Processor23 WARN \plugin.report.worklo...Hi Vincent,
2007-12-12 12:19:48,753 http-8090-Processor23 WARN [plugin.report.workload.WorkloadHelper] Report Component Class [class java.util.Date] not yet supported ...
pls chk the error, and help me
Jan 03, 2008
Amit Khullar says:
HI I have installed the Kameleot ver 3.10.1.20on Jira 3.11 Ent Ed when I goto th...HI I have installed the Kameleot ver 3.10.1.20on Jira 3.11 Ent Ed when I goto the Adminstration menu and click on the Plugins > Setting link it gives me this error below in the JIRA Log
2008-01-03 15:00:47,565 http-8080-Processor23 ERROR [velocity] RHS of #set statement is null. Context will not be modified. secure/admin/plugins/settings/ViewPluginsSettings.vm [line 2, column 8]
2008-01-03 15:00:47,565 http-8080-Processor23 ERROR [velocity] RHS of #set statement is null. Context will not be modified. secure/admin/plugins/settings/ViewPluginsSettings.vm [line 2, column 8]
2008-01-03 15:00:47,565 http-8080-Processor23 ERROR [velocity] Method getValue threw exception for reference $settingManager in template secure/admin/plugins/settings/ViewPluginsSettings.vm at [2,31]
2008-01-03 15:00:47,565 http-8080-Processor23 ERROR [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at com.atlassian.jira.config.settings.managers.IntegerSettingManager.getValue(IntegerSettingManager.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197)
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.parser.node.ASTExpression.value(ASTExpression.java:51)
at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:172)
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.directive.Foreach.render(Foreach.java:166)
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.VelocimacroProxy.render(VelocimacroProxy.java:172)
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.directive.Foreach.render(Foreach.java:166)
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.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:46)
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:73)
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:43)
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:50)
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.AbstractJohnsonFilter.doFilter(AbstractJohnsonFilter.java:72)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:350)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.atlassian.gzipfilter.GzipFilter.doFilter(GzipFilter.java:89)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.Applicati