Hello,
While migrating our internal plugin to Jira 10.3.11 we are experiencing the behavior described here: Jira templates and JSPs When invoking the an webwork action, the browser return a 404 and the logs contain:
2025-10-21 14:57:06,556-0400 http-nio-8080-exec-9 DEBUG cc200206 897x4729x1 1lepr4z 10.7.21.105 /secure/PrismClonePlusPropagate!default.jspa [c.a.j.web.dispatcher.JiraWebworkViewDispatcher] Action Result input → View Name: /secure/views/prism-jira-clone-plus-propagate.jsp
2025-10-21 14:57:06,557-0400 http-nio-8080-exec-9 DEBUG cc200206 897x4729x1 1lepr4z 10.7.21.105 /secure/PrismClonePlusPropagate!default.jspa [c.a.j.web.filters.SitemeshPageFilter] PathExclusionFilter[sitemesh].filter decorated filter ACCEPTED for servlet path [/secure/views/prism-jira-clone-plus-propagate.jsp]
2025-10-21 14:57:06,558-0400 http-nio-8080-exec-9 DEBUG cc200206 897x4729x1 1lepr4z 10.7.21.105 /secure/PrismClonePlusPropagate!default.jspa [c.a.j.w.filters.annotations.JspChecker] [SECURITY ANNOTATION CHECK] view.requested.by.action=/secure/views/prism-jira-clone-plus-propagate.jsp, but servlet ‘action’ is not a JSP
2025-10-21 14:57:06,559-0400 http-nio-8080-exec-9 DEBUG cc200206 897x4729x1 1lepr4z 10.7.21.105 /secure/PrismClonePlusPropagate!default.jspa [c.a.j.web.dispatcher.JiraWebworkViewDispatcher] Action Result success → View Name: :action-soy-templates/JIRA.Templates.errors.error404
The JSP files are present in folder /atlassian-jira/secure/views/plugins/.
The webwork is also defined as prescribed in documentation:
<webwork1 key="com.ciena.prism.jira.plugins.clone-plus.webwork" name="PRISM Jira Clone Plus Issue Webwork Module"
class="java.lang.Object">
<description>PRISM Jira Clone plus issue webwork module</description>
<actions>
<!-- Clone plus start (clone++) -->
<action name="com.ciena.prism.jira.plugins.cloneplus.web.action.issue.PrismClonePlusStart"
alias="PrismClonePlusStart">
<view name="error">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-start.jsp
</view>
<view name="invalidlicense">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-start.jsp
</view>
<view name="success">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-start.jsp
</view>
<view name="input">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-start.jsp
</view>
</action>
<!-- Clone plus details (clone+) -->
<action name="com.ciena.prism.jira.plugins.cloneplus.web.action.issue.PrismClonePlusDetails"
alias="PrismClonePlusDetails">
<view name="input">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-details.jsp
</view>
<view name="invalidlicense">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-details.jsp
</view>
<view name="success">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-details.jsp
</view>
<view name="error">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-details.jsp
</view>
</action>
<!-- Clone plus details (propagate) -->
<action name="com.ciena.prism.jira.plugins.cloneplus.web.action.issue.PrismClonePlusPropagate"
alias="PrismClonePlusPropagate">
<view name="input">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-propagate.jsp
</view>
<view name="invalidlicense">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-propagate.jsp
</view>
<view name="success">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-propagate.jsp
</view>
<view name="error">/secure/views/plugins/prism-jira-clone-plus/prism-jira-clone-plus-propagate.jsp
</view>
</action>
</actions>
</webwork1>
This is working fine in Jira 9.12, but in Jira 10.3 when we click a corresponding menu item, we get 404. Is the JspChecker reporting “not a JSP” expected? Or did something change in the webwork configuration in Jira 10?
This is preventing our migration, please help.