-
Suggestion
-
Resolution: Won't Do
-
None
-
Oracle users
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
On Oracle, we have a size limitation for issue Description and Comment fields of 4000 characters.
So, if you add a description or a comment that is greater than that, you get an error:
Exception: com.opensymphony.workflow.InternalWorkflowException: An unknown exception occured while executing FunctionProvider: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFieldFunction
at com.opensymphony.workflow.AbstractWorkflow.executeFunction(AbstractWorkflow.java:934)
at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1107)
at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:366)
at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:80)
at com.atlassian.jira.issue.IssueUtils.createIssue(IssueUtils.java:65)
The problem here is that there is no hint as to what caused the error. It would be better to be able to give an error:
"Your comment is too large. Consider creating an attachment."
Its practically impossible from the Entity Engine exception, to programmatically work out what happened (even the error message depends on what version of oracle)
The only other thing to do is to make it part of the Web Action validation - thereby forcing a limit on everyone.
This would actually be a good thing, because they might otherwise end up hitting this limitation when changing databases (as we did). Especially since HSQLDB in the stand-alone version doesnt have any limit....
- is duplicated by
-
JRASERVER-2441 NPE when creating new issue
- Closed
-
JRASERVER-2820 Enter more than 6000+ char's in the issue description field. It throws java exception during issue edit event.
- Closed
-
JRASERVER-3745 java.lang.reflect.UndeclaredThrowableException
- Closed
-
JRASERVER-3798 Import fails -Data too large exception
- Closed
-
JRASERVER-2482 Lengthy comment validation during create new issue & add comment
- Closed
-
JRASERVER-2994 Oracle import fails because text field greater than 4000 characters
- Closed
-
JRASERVER-3391 Funny Bounced message in the logs
- Closed
-
JRASERVER-4490 bad error message
- Closed
-
JRASERVER-4608 When adding comments over 300k, a 500 error is thrown
- Closed
-
JRASERVER-2444 bad error message with long descriptions
- Closed
-
JRASERVER-4011 More useful error message required
- Closed
- is related to
-
JRASERVER-3563 Description greater than 4k character throws an exception: java.lang.reflect.UndeclaredThrowableException
- Closed
-
JRASERVER-4180 Fix error handling when > 4000 character limit is encountered in Oracle
- Closed
-
JRASERVER-4361 Cannot store workflows of over 4000 characters in Oracle
- Closed
- relates to
-
JRACLOUD-2152 Error reporting of Oracle Text Field Size limitations
- Closed
-
JRASERVER-1273 Review database mappings for reserved words
- Closed