We can't create this issue for you right now, it could be due to unsupported content you've entered

[Jasveen Singh]

I am unable to create ticket for some projects after upgrading Postgres from 9.3 to v 9.6 and Jira from 7.13.5 to v 8.5.0.

These projects use the same workflow.

Error - We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file.

Error in log file - [9:49 AM]  2019-11-13 13:39:23,224 http-nio-8080-exec-3 ERROR jfsingh 819x163874x1 qa51m5  /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue: com.atlassian.jira.exception.CreateException: Error while executing TransitionIssueFunction: groovy.lang.MissingPropertyException: No such property: Sub for class: script15736123274661242956866: root cause: No such property: Sub for class: script15736123274661242956866     at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:600)     at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:501)     at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssue(RequestCachingIssueManager.java:195)     at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:253)     at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:221)     ... 2 filtered     at java.lang.reflect.Method.invoke(Method.java:498)     at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)     at com.sun.proxy.$Proxy36.create(Unknown Source)     ... 2 filtered     at java.lang.reflect.Method.invoke(Method.java:498)     at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:131)     at com.sun.proxy.$Proxy36.create(Unknown Source)     at com.atlassian.jira.quickedit.action.QuickCreateIssue.doExecute(QuickCreateIssue.java:308)     ... 1 filtered     at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)     ... 7 filtered     at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)     ... 48 filtered     at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:62)     ... 7 filtered     at com.atlassian.jira.plugin.mobile.web.filter.MobileAppRequestFilter.doFilter(MobileAppRequestFilter.java:37)     ... 4 filtered     at com.atlassian.jira.plugin.mobile.login.MobileLoginSuccessFilter.doFilter(MobileLoginSuccessFilter.java:54)     ... 3 filtered     at com.atlassian.diagnostics.internal.platform.monitor.http.HttpRequestMonitoringFilter.doFilter(HttpRequestMonitoringFilter.java:55)     ... 8 filtered     at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)     ... 62 filtered     at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)     ... 1 filtered     at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)     ... 39 filtered     at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)     ... 10 filtered     at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)     ... 4 filtered     at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)     ... 26 filtered     at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)     ... 24 filtered     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)     at java.lang.Thread.run(Thread.java:748) Caused by: com.atlassian.jira.workflow.WorkflowException: Error while executing TransitionIssueFunction: groovy.lang.MissingPropertyException: No such property: Sub for class: script15736123274661242956866: root cause: No such property: Sub for class: script15736123274661242956866     at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:773)     at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:592)     ... 276 more Caused by: com.opensymphony.workflow.WorkflowException: Error while executing TransitionIssueFunction: groovy.lang.MissingPropertyException: No such property: Sub for class: script15736123274661242956866: root cause: No such property: Sub for class: script15736123274661242956866     at com.innovalog.jmwe.plugins.functions.AbstractPreserveChangesPostFunction.execute(AbstractPreserveChangesPostFunction.java:131)     at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1407)     at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:606)     at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:754)     ... 277 more Caused by: groovy.lang.MissingPropertyException: No such property: Sub for class: script15736123274661242956866     at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:65)     at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:51)     at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:309)     at script15736123274661242956866.run(script15736123274661242956866.groovy:1)     at com.innovalog.groovy.GroovyExpression.eval(GroovyExpression.java:165)     at com.innovalog.groovy.GroovyExpression.evalAsBoolean(GroovyExpression.java:116)     at com.innovalog.jmwe.plugins.functions.TransitionIssueFunction.executeFunction(TransitionIssueFunction.java:101)     at com.innovalog.jmwe.plugins.functions.AbstractPreserveChangesPostFunction.execute(AbstractPreserveChangesPostFunction.java:126)     ... 281 more 2019-11-13 13:43:08,274 plugin-transaction-0 INFO      [c.a.jira.plugin.PluginTransactionListener] [plugin-transaction] numberStartEvents:650, numberEndEvents:650, numberSendEvents:387, numberEventsInTransactions:14369, numberOfPluginEnableEvents:287 2019-11-13 13:48:08,274 plugin-transaction-0 INFO      [c.a.jira.plugin.PluginTransactionListener] [plugin-transaction] numberStartEvents:650, numberEndEvents:650, numberSendEvents:387, numberEventsInTransactions:14369, numberOfPluginEnableEvents:287 2019-11-13 13:52:15,269 http-nio-8080-exec-53 WARN jfsingh 832x164103x2 3z5oyb /rest/plugins/1.0/installed-marketplace [c.a.upm.pac.PacClientImpl] The request to check for add-on updates may take longer than expected because 199 user-installed add-ons are installed. This may impact the performance of loading the Manage Add-ons page. 2019-11-13 13:52:36,049 http-nio-8080-exec-12 INFO jfsingh 832x164127x1 3z5oyb /rest/plugins/1.0/com.innovalog.jmwe.jira-misc-workflow-extensions-key [c.a.plugin.manager.DefaultPluginManager] To disable plugins '[com.innovalog.jmwe.jira-misc-workflow-extensions]', we need to first disable all dependent enabled plugins: [] 2019-11-13 13:52:36,049 http-nio-8080-exec-12 INFO jfsingh 832x164127x1 3z5oyb  /rest/plugins/1.0/com.innovalog.jmwe.jira-misc-workflow-extensions-key [c.a.plugin.manager.DefaultPluginManager] Disabling com.innovalog.jmwe.jira-misc-workflow-extensions 2019-11-13 13:52:36,227 http-nio-8080-exec-12 DEBUG jfsingh 832x164127x1 3z5oyb /rest/plugins/1.0/com.innovalog.jmwe.jira-misc-workflow-extensions-key [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] onPluginDisabledEvent removing delegate for [com.innovalog.jmwe.jira-misc-workflow-extensions] 2019-11-13 13:53:08,274 plugin-transaction-0 INFO      [c.a.jira.plugin.PluginTransactionListener] [plugin-transaction] numberStartEvents:651, numberEndEvents:651, numberSendEvents:388, numberEventsInTransactions:14529, numberOfPluginEnableEvents:287  

[Fadoua]

@Jasveen Singh 

Is this test or Production environment?

Did you do the DB upgrade and Application upgrade at the same time?

Can you please check Catalina log file and share the errors you are seeing there after hiding any confidential information?

Best,

Fadoua

[Jasveen Singh]

Hi Fadoua,

This is in test environment and data has been exported from Production env.

Yes, first DB was updated and subsequently Jira was upgraded once DB upgrade completed.

Strangely the i am able to create tickets for some projects but not for others.

Description section has detailed log with error. Please let me know if you need more info.

[Fadoua]

@Jasveen Singh 

Are you using in your instance Groovy scripts? Or do you have ScriptRunner installed? Did you check if everything is working fine with ScriptRunner if installed?

[Jasveen Singh]

@Fadoua 

I think I have narrowed down the error to the JMWE add on v. 6.1.3 Transition current issue
Post-function.

The first applicable transition from this list will be triggered on the issue:

• 5 of any workflow

Run this post-function only if the following condition is true:

issuetype = Sub-task

Once I remove this post function I am able to create issues.

Could you please let me know how

1) I can find out what id 5 of any workflow relates to. So that I can create a similar function to attach and test.

2) Why is this throwing error in Jira v8.5.0 and Not in Jira 7.13.5

[David Fischer]

Hi @Jasveen Singh ,

the reason why you are seeing this error is because that post function has an incorrect Conditional Execution script. You need to fix it. 
This error was there before you upgraded Jira and JMWE, but before JMWE 6.1, errors like this were, by default, only logged to atlassian-jira.log and not reported to the user. In JMWE 6.1, these errors are now reported to the user but only if the user is a Jira administrator. You can change that behavior on the JMWE configuration admin page, but I recommend you correct your script instead. 

[Jasveen Singh]

Thanks for the update. So basically this was ignored and Jira tickets(story,tasks etc) could be created regardless of this error in previous versions. I think that explains why it works in previous Jira versions.

• 5 of any workflow

Could you please let me know is there any way to figure out what id 5 means as I tried to look at transition picker and it didn't list any with that id. (and I if associate it with some id that's not there it is bound to fail)

This would help me fix by replicating the original post function as close as possible.

Also, do I need to manually enter any workflow to associate it to any workflow as again there is no such option in transition picker.

[Fadoua]

@Jasveen Singh  I think the best way to find ID is by running a query against the DB.

select pname, id from issuestatus where id = '5'

@David Fischer Thanks for the help! I could see from the logs that a script is behind the issue. However it is hard to tell which plugin when you don't know what's in the instance.

Best,

Fadoua

[David Fischer]

My guess is that "5" is simply not a valid transition ID (by the way, it's a Transition ID, not a Status ID). But the post-function won't fail, it just won't do anything - which is already the case because of the incorrect conditional execution script. So basically the Transition Current Issue post-function currently does nothing.

[Jasveen Singh]

@David Fischer  @Fadoua 

This was really helpful. Thanks.