Jira UI throws 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." while trying to create an issue
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
While trying to Create an Issue, Jira might throw this generic error on the UI:
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.
Please note that this error on the UI is quite generic and this KB might not apply in every case. Please follow the Diagnosis section for the specific error we're discussing here and to determine whether this KB is applicable to you.
Environment
Jira Data Center with Jira Workflow Toolbox app
Diagnosis
In the atlassian-jira.log, we see the following error while trying to create an issue. As you can see in the stack trace, the CreateException comes from the operation done by one of this app's classes com.fca.jira.plugins.workflowToolbox.MathExpressionsValidator.validate
2024-03-27 06:46:20,844-0500 https-jsse-nio-8443-exec-16 url: /secure/QuickCreateIssue.jspa; user: xxx ERROR xxx 406x2937406x4 2diwc5 X.X.X.X /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue:
com.atlassian.jira.exception.CreateException: ERROR IN BOOLEAN EXPRESSION "toLowerCase(%{issue.summary}) NOT IN textOnStringList(fieldValue(%{issue.summary}, filterByIssueType(getIssuesFromProjects("XXXX"), "XXXXX")), toLowerCase(^%))" : *** Memory limit exceeded by function getIssuesFromProjects( XXXX ). Returning at least 52412 when the limit is 50000.
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:585)
at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:486)
at com.atlassian.jira.issue.managers.RequestCachingIssueManager.createIssue(RequestCachingIssueManager.java:195)
...<TRIMMED>...
Caused by: com.atlassian.jira.workflow.WorkflowException: ERROR IN BOOLEAN EXPRESSION "toLowerCase(%{issue.summary}) NOT IN textOnStringList(fieldValue(%{issue.summary}, filterByIssueType(getIssuesFromProjects("XXXX"), "Build Package")), toLowerCase(^%))" : *** Memory limit exceeded by function getIssuesFromProjects( XXXX ). Returning at least 52412 when the limit is 50000.
at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:773)
...<TRIMMED>...
Caused by: com.opensymphony.workflow.WorkflowException: ERROR IN BOOLEAN EXPRESSION "toLowerCase(%{issue.summary}) NOT IN textOnStringList(fieldValue(%{issue.summary}, filterByIssueType(getIssuesFromProjects("XXXX"), "Build Package")), toLowerCase(^%))" : *** Memory limit exceeded by function getIssuesFromProjects( XXXX ). Returning at least 52412 when the limit is 50000.
at com.fca.jira.plugins.workflowToolbox.MathExpressionsValidator.validate(MathExpressionsValidator.java:64)
at com.opensymphony.workflow.AbstractWorkflow.verifyInputs(AbstractWorkflow.java:1466)Jira Workflow Toolbox app provides additional features on Jira Workflows specifically in this case Conditions / Validators. In this case, we saw the same validator expression just like the one in the logs above:
Cause
The primary error during the com.fca.jira.plugins.workflowToolbox.MathExpressionsValidator.validate method was the following:
*** Memory limit exceeded by function getIssuesFromProjects( <PROJ> ). Returning at least 52412 when the limit is 50000.As it turns out this 50000 is the maximum limit by default set by the app if you go to https://<JIRA_BASE_URL>/secure/admin/jwt/performanceSettings.jspa and look at the "Maximum number of issues used in expression parser functions*"
Here is the vendor documentation on this topic: Performance settings
Solution
- We highly recommend that you reach out to the App vendor directly to make sure you get expert advice from JWT support.
- Calibrate the expression to reduce the number of issues in scope and bring it below the 50000 limit
- You may want to try increasing the value for the "Maximum number of issues used in expression parser functions*" parameter and try to set it above the
Xvalue mentioned in the error "Returning at least X when the limit is 50000" to resolve the problem as well.
However, please note that increasing this limit has performance penalty. Please consult with the app vendor directly to gain further insights on what's best for you.