-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Space Administration - Workflows and statuses
-
2
-
Severity 3 - Minor
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
When creating a global transition that goes back to itself, clicking on 'conditions' or 'validators' etc. leads to an error page
Steps to Reproduce
- Create a transition in a workflow in diagram mode
- Set from status to 'any'
- Set to status to 'itself'
- Name status and click add
- High light the status and click on conditions or validators in the right panel
Expected Results
Property page for conditions or validators etc opens.
Actual Results
JIRA directs to this URL:
http://localhost:8080/jira/secure/admin/workflows/ViewWorkflowTransition.jspa?workflowMode=live&workflowName=classic+default+workflow&workflowTransition=711&descriptorTab=conditions&workflowStep=undefined
And displays a 404 'oops you've found a dead link'
The below exception is thrown in the xxxxxxx.log file:
2016-12-29 09:31:48,278 http-nio-8080-exec-22 uri:/jira/secure/404.jspa username: ERROR [c.a.j.w.util.component.RequestComponentManager] For input string: "undefined" java.lang.NumberFormatException: For input string: "undefined" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:580) at java.lang.Integer.parseInt(Integer.java:615) at com.atlassian.jira.web.util.component.RequestComponentManager.injectWorkflow(RequestComponentManager.java:85) at com.atlassian.jira.web.util.component.RequestComponentManager.getContainer(RequestComponentManager.java:42) at com.atlassian.jira.web.util.component.PicoWebworkObjectCreator.instantiate(PicoWebworkObjectCreator.java:30) at webwork.util.injection.ObjectFactory.instantiate(ObjectFactory.java:47) at com.atlassian.jira.config.webwork.JiraActionFactory$JiraPluginActionFactory.instantiateAction(JiraActionFactory.java:421) at com.atlassian.jira.config.webwork.JiraActionFactory$JiraPluginActionFactory.getActionImpl(JiraActionFactory.java:397) at webwork.action.factory.PrefixActionFactoryProxy.getActionImpl(PrefixActionFactoryProxy.java:109) at webwork.action.factory.JspActionFactoryProxy.getActionImpl(JspActionFactoryProxy.java:59) at webwork.action.factory.CommandActionFactoryProxy.getActionImpl(CommandActionFactoryProxy.java:60) at com.atlassian.jira.config.webwork.LookupAliasActionFactoryProxy.getActionImpl(LookupAliasActionFactoryProxy.java:61) at webwork.action.factory.CommandActionFactoryProxy.getActionImpl(CommandActionFactoryProxy.java:60) at webwork.action.factory.ContextActionFactoryProxy.getActionImpl(ContextActionFactoryProxy.java:36) at webwork.action.factory.PrepareActionFactoryProxy.getActionImpl(PrepareActionFactoryProxy.java:37) at com.atlassian.jira.config.webwork.JiraActionFactory$SafeParameterSettingActionFactoryProxy.getActionImpl(JiraActionFactory.java:147) at webwork.action.factory.ChainingActionFactoryProxy.getActionImpl(ChainingActionFactoryProxy.java:53) at com.atlassian.jira.config.webwork.JiraActionFactory.getActionImpl(JiraActionFactory.java:301) ... 2 filtered at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) ... 11 filtered at com.atlassian.ams.shipit.servlet.filter.TomcatThreadFilter.doFilter(TomcatThreadFilter.java:70) ... 81 filtered at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)
Notes
(Optional - If Necessary)
Workaround
There is no workaround.
- is related to
-
JRASERVER-63666 Workflow condition leads to error page
-
- Gathering Impact
-