com.atlassian.jira.exception.CreateException

Atlassian JIRA | Nick Mason [Atlassian] | 3 months ago
  1. 0

    h3. Steps to reproduce # Create a new JIRA project. # Edit the workflow that's generated and add the "Set Field Value from Parent" post function to the initial Create transition, tick the "Add source value(s) to destination field" box. # Create an issue with no components set. # Create a subtask of that issue. h3. Expected results The subtask is created normally. h3. Actual results JIRA displays an error at the top of the Create Issue screen: {quote} 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. {quote} And this stack trace is shown in the logs: {code:java} 2016-08-22 11:16:25,338 http-nio-3010-exec-9 ERROR admin 676x88x1 u56vut 59.167.133.100 /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue: com.atlassian.jira.exception.CreateException at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:588) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:494) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:231) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:200) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... 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.$Proxy289.create(Unknown Source) ... 3 filtered at java.lang.reflect.Method.invoke(Method.java:498) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:136) at com.sun.proxy.$Proxy289.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:67) ... 7 filtered at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at com.atlassian.jira.servlet.WebExceptionCheckingServlet.delegate(WebExceptionCheckingServlet.java:86) at com.atlassian.jira.servlet.WebExceptionCheckingServlet.service(WebExceptionCheckingServlet.java:32) ... 30 filtered at com.atlassian.servicedesk.internal.web.OperationalStatusAwareHttpFilter.doFilter(OperationalStatusAwareHttpFilter.java:31) ... 4 filtered at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:62) ... 17 filtered at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21) ... 47 filtered at com.atlassian.plugin.connect.plugin.auth.scope.ApiScopingFilter.doFilter(ApiScopingFilter.java:81) ... 14 filtered at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:76) ... 1 filtered at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:74) ... 29 filtered at com.atlassian.studio.jira.homepage.CloudHomepageFilter$Action.lambda$nextInFilterChain$1(CloudHomepageFilter.java:110) at com.atlassian.studio.jira.homepage.CloudHomepageFilter.doFilter(CloudHomepageFilter.java:68) ... 20 filtered at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30) ... 5 filtered at com.atlassian.plugin.connect.plugin.auth.oauth2.DefaultSalAuthenticationFilter.doFilter(DefaultSalAuthenticationFilter.java:76) ... 3 filtered at com.atlassian.plugin.connect.plugin.auth.user.ThreeLeggedAuthFilter.doFilter(ThreeLeggedAuthFilter.java:110) ... 3 filtered at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.lambda$invokeFilterChain$0(CustomerContextSettingFilter.java:181) at com.atlassian.servicedesk.internal.utils.context.ReentrantThreadLocalBasedCodeContext.rteInvoke(ReentrantThreadLocalBasedCodeContext.java:142) at com.atlassian.servicedesk.internal.utils.context.ReentrantThreadLocalBasedCodeContext.runOutOfContext(ReentrantThreadLocalBasedCodeContext.java:94) at com.atlassian.servicedesk.internal.utils.context.CustomerContextServiceImpl.runOutOfCustomerContext(CustomerContextServiceImpl.java:64) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.outOfCustomerContext(CustomerContextSettingFilter.java:174) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilterImpl(CustomerContextSettingFilter.java:130) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilter(CustomerContextSettingFilter.java:121) ... 4 filtered at com.atlassian.jwt.internal.servlet.JwtAuthFilter.doFilter(JwtAuthFilter.java:32) ... 8 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) ... 29 filtered at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25) ... 7 filtered at com.atlassian.jira.util.zipkin.ZipkinTracingFilter.lambda$doFilter$1(ZipkinTracingFilter.java:53) at com.github.kristofa.brave.servlet.BraveServletFilter.doFilter(BraveServletFilter.java:59) at com.atlassian.jira.util.zipkin.ZipkinTracingFilter.doFilter(ZipkinTracingFilter.java:41) ... 22 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) Caused by: com.atlassian.jira.workflow.WorkflowException at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:871) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:580) ... 304 more Caused by: java.lang.NullPointerException at com.atlassian.jira.bc.project.component.DefaultProjectComponentManager$1.get(DefaultProjectComponentManager.java:77) at com.atlassian.jira.util.collect.TransformingIterator.next(TransformingIterator.java:34) at com.atlassian.jira.util.collect.CollectionUtil.foreach(CollectionUtil.java:39) at com.atlassian.jira.util.collect.CollectionUtil.toList(CollectionUtil.java:65) at com.atlassian.jira.util.collect.CollectionUtil.transform(CollectionUtil.java:127) at com.atlassian.jira.util.collect.CollectionUtil.transform(CollectionUtil.java:148) at com.atlassian.jira.bc.project.component.DefaultProjectComponentManager.updateIssueValue(DefaultProjectComponentManager.java:209) at com.atlassian.jira.bc.project.component.DefaultProjectComponentManager.updateIssueProjectComponents(DefaultProjectComponentManager.java:197) at com.atlassian.jira.issue.fields.ComponentsSystemField.updateIssueValue(ComponentsSystemField.java:442) at com.atlassian.jira.issue.fields.ComponentsSystemField.updateValue(ComponentsSystemField.java:415) at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:850) ... 305 more {code} h3. Notes * This *only* occurs when the "Add source value(s) to destination field" field in the post function is ticked. * The subtask _is_ created but not as a subtask of the parent issue but as a regular standard issue (despite having a type of "Sub-task"). * This bug only occurs in JIRA 1000.245.0 and later, it can't be reproduced in the previous production release (1000.217.2). This also occurs for Affects and Fix Versions, but not Labels.

    Atlassian JIRA | 3 months ago | Nick Mason [Atlassian]
    com.atlassian.jira.exception.CreateException
  2. 0

    h4. +Summary+ A Number custom field in JIRA has type Numeric(18,6) in table *customfieldvalue* in the database (MS SQL). That means, it supports a maximum of 18 digits only, 12 before and 6 after the decimal point e.g. 111222333444.555666 However, when trying to enter a very big value e.g. 111222333444555666777888999, the field says it supports the maximum value of 100000000000000, which is 15 digits before the decimal point. This is incorrect, as it exceeds the number of digits before the decimal point and there will be not enough space for the decimal digits. And the fact is, *the field doesn't accept a number which has more than 12 digits before the decimal point*. h4. +Steps to reproduce+ # create a Number custom field # create an issue and enter the following value for the field: 111222333444555666777888999 # the field will say the maximum value allowed is 100000000000000 !number.png|thumbnail! # now enter a different value with more than 12 and less than 15 digits before the decimal point e.g. 1000000000000 (13 digits) # click Create h4. +Expected behavior+ # JIRA should accept the value as it's less than the maximum value allowed # The issue should be created with the Number value and indexed normally h4. +Actual behavior+ # JIRA throws an error: !create.png|thumbnail! # The following error is seen in _JIRA_Home/log/atlassian-jira.log_: {noformat} 2016-04-29 03:01:20,269 http-nio-8714-exec-17 ERROR admin 181x2025x1 54hyjn 0:0:0:0:0:0:0:1 /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue: com.atlassian.jira.exception.CreateException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:CustomFieldValue][parentkey,null][customfield,10101][issue,10039][id,10042][numbervalue,1.0E12] (SQL Exception while executing the following:INSERT INTO dbo.customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation)) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:588) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:494) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:230) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:199) at sun.reflect.GeneratedMethodAccessor1330.invoke(Unknown Source) ... 1 filtered ... Caused by: java.sql.DataTruncation: Data truncation at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:386) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:613) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:572) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:727) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:673) ... 259 more {noformat} # The issue is still created in JIRA without the Number value - this can be seen from the database: !database.png|thumbnail! (i) in my test, 39 issues are created but only 15 Number values are accepted # However, the created issue is not indexed, so it's invisible from Issue Navigator and users might think it's not created at all: !index.png|thumbnail! (i) only the issues whose Number value is accepted are indexed h4. +Notes+ # Re-indexing JIRA will make all the issues visible in Issue Navigator # Only values up to 999999999999.999938 (12 digits before the decimal point) will be accepted and rounded up to 100000000000000 (13 digits), like the issue TEST-37 in [^index.png]. It's however stored as 999999999999.999880 (12 digits before the decimal point) in the database like in [^database.png]. # More than 6 decimal digits can be accepted (which is expected as they can be rounded) h4. +Suggestion+ # The warning message about the maximum value allowed must be correct # Values should be displayed exactly the same as they're stored in the database

    Atlassian JIRA | 7 months ago | Andy Nguyen [Atlassian]
    com.atlassian.jira.exception.CreateException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:CustomFieldValue][parentkey,null][customfield,10101][issue,10039][id,10042][numbervalue,1.0E12] (SQL Exception while executing the following:INSERT INTO dbo.customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation))
  3. 0

    I use the following validator: !validator.PNG|thumbnail! This validator works fine when used in a transtion from one status to another. But it does not work correctly when it is used in the initial transtion of a workflow - when the issue gets created. In this case, it sill validates correct. But when the input does not match the pattern, the users do not get the configured error message. They get the following message from JIRA: bq. 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. The log contains in this case the following exception: {code} com.atlassian.jira.exception.CreateException: Die Kontonummer entspricht nicht der vorgegebenen Syntax. Bitte definiertes Format einhalten: 10 Ziffern oder 10 Ziffern plus ein abschlie▒<9F>endes "a" für alte/archivierte Kontonummern. Son stige Zeichen sind nicht erlaubt! at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:588) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:494) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:230) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:199) at sun.reflect.GeneratedMethodAccessor1315.invoke(Unknown Source) ... 1 filtered at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26) at com.sun.proxy.$Proxy45.create(Unknown Source) ... 2 filtered at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:136) at com.sun.proxy.$Proxy45.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:729) ... 17 filtered at com.idalko.jira.plugins.igrid.WebResourceIncludeFilter.doFilter(WebResourceIncludeFilter.java:160) ... 41 filtered at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:59) ... 23 filtered at com.intenso.jira.contentinjection.filter.ContentInjectionFilter.doFilter(ContentInjectionFilter.java:71) ... 3 filtered at org.kantega.atlaskerb.AtlasKerberosFilter.doFilter(AtlasKerberosFilter.java:80) ... 3 filtered at org.kantega.atlaskerb.AtlasKerberosFilter.doFilter(AtlasKerberosFilter.java:80) ... 34 filtered at com.quisapps.jira.fieldsecurity.filter.FieldSecurityFilter.doFilterChainWithProfiling(FieldSecurityFilter.java:228) at com.quisapps.jira.fieldsecurity.filter.FieldSecurityFilter.doFilterInterval(FieldSecurityFilter.java:155) at com.quisapps.jira.fieldsecurity.filter.FieldSecurityFilter.doFilter(FieldSecurityFilter.java:58) ... 11 filtered at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:70) ... 20 filtered at org.kantega.atlaskerb.AtlasKerberosFilter.doFilter(AtlasKerberosFilter.java:80) ... 21 filtered at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.lambda$invokeFilterChain$0(CustomerContextSettingFilter.java:169) at com.atlassian.servicedesk.internal.util.scala.ScalaJavaInterOp$1.apply(ScalaJavaInterOp.java:25) at com.atlassian.servicedesk.internal.utils.context.CustomerContextUtil$.outOfCustomerContext(CustomerContextUtil.scala:48) at com.atlassian.servicedesk.internal.utils.context.CustomerContextUtil.outOfCustomerContext(CustomerContextUtil.scala) at com.atlassian.servicedesk.internal.utils.context.CustomerContextServiceImpl.outOfCustomerContext(CustomerContextServiceImpl.java:24) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.outOfCustomerContext(CustomerContextSettingFilter.java:164) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilterImpl(CustomerContextSettingFilter.java:120) at com.atlassian.servicedesk.internal.web.CustomerContextSettingFilter.doFilter(CustomerContextSettingFilter.java:112) ... 12 filtered at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at net.bull.javamelody.JiraMonitoringFilter.doFilter(JiraMonitoringFilter.java:105) ... 45 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) at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:760) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:580) ... 280 more at org.swift.jira.cw.validators.ConditionedValidator.process(ConditionedValidator.java:117) at com.atlassian.jira.workflow.SkippableValidator.validate(SkippableValidator.java:45) at com.opensymphony.workflow.AbstractWorkflow.verifyInputs(AbstractWorkflow.java:1512) at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1203) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:615) at com.atlassian.jira.workflow.OSWorkflowManager.createIssue(OSWorkflowManager.java:741) ... 281 more {code} Do I have to use an other configuration in the initial transition or is this a bug in JIRA or UoT?

    JIRA | 5 months ago | Wolfgang Fellner
    com.atlassian.jira.exception.CreateException: Die Kontonummer entspricht nicht der vorgegebenen Syntax. Bitte definiertes Format einhalten: 10 Ziffern oder 10 Ziffern plus ein abschlie▒<9F>endes "a" für alte/archivierte Kontonummern. Son stige Zeichen sind nicht erlaubt!
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h4. +Summary+ A Number custom field in JIRA has type Numeric(18,6) in table *customfieldvalue* in the database (MS SQL). That means, it supports a maximum of 18 digits only, 12 before and 6 after the decimal point e.g. 111222333444.555666 However, when trying to enter a very big value e.g. 111222333444555666777888999, the field says it supports the maximum value of 100000000000000, which is 15 digits before the decimal point. This is incorrect, as it exceeds the number of digits before the decimal point and there will be not enough space for the decimal digits. And the fact is, *the field doesn't accept a number which has more than 12 digits before the decimal point*. h4. +Steps to reproduce+ # create a Number custom field # create an issue and enter the following value for the field: 111222333444555666777888999 # the field will say the maximum value allowed is 100000000000000 !number.png|thumbnail! # now enter a different value with more than 12 and less than 15 digits before the decimal point e.g. 1000000000000 (13 digits) # click Create h4. +Expected behavior+ # JIRA should accept the value as it's less than the maximum value allowed # The issue should be created with the Number value and indexed normally h4. +Actual behavior+ # JIRA throws an error: !create.png|thumbnail! # The following error is seen in _JIRA_Home/log/atlassian-jira.log_: {noformat} 2016-04-29 03:01:20,269 http-nio-8714-exec-17 ERROR admin 181x2025x1 54hyjn 0:0:0:0:0:0:0:1 /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue: com.atlassian.jira.exception.CreateException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:CustomFieldValue][parentkey,null][customfield,10101][issue,10039][id,10042][numbervalue,1.0E12] (SQL Exception while executing the following:INSERT INTO dbo.customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation)) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:588) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:494) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:230) at com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:199) at sun.reflect.GeneratedMethodAccessor1330.invoke(Unknown Source) ... 1 filtered ... Caused by: java.sql.DataTruncation: Data truncation at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:386) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:613) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:572) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:727) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:673) ... 259 more {noformat} # The issue is still created in JIRA without the Number value - this can be seen from the database: !database.png|thumbnail! (i) in my test, 39 issues are created but only 15 Number values are accepted # However, the created issue is not indexed, so it's invisible from Issue Navigator and users might think it's not created at all: !index.png|thumbnail! (i) only the issues whose Number value is accepted are indexed h4. +Notes+ # Re-indexing JIRA will make all the issues visible in Issue Navigator # Only values up to 999999999999.999938 (12 digits before the decimal point) will be accepted and rounded up to 100000000000000 (13 digits), like the issue TEST-37 in [^index.png]. It's however stored as 999999999999.999880 (12 digits before the decimal point) in the database like in [^database.png]. # More than 6 decimal digits can be accepted (which is expected as they can be rounded) h4. +Suggestion+ # The warning message about the maximum value allowed must be correct # Values should be displayed exactly the same as they're stored in the database

    Atlassian JIRA | 7 months ago | Andy Nguyen [Atlassian]
    com.atlassian.jira.exception.CreateException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:CustomFieldValue][parentkey,null][customfield,10101][issue,10039][id,10042][numbervalue,1.0E12] (SQL Exception while executing the following:INSERT INTO dbo.customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) (Data truncation))

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.jira.exception.CreateException

      No message provided

      at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue()
    2. com.atlassian.jira
      DefaultIssueService.create
      1. com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:588)
      2. com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:494)
      3. com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:231)
      4. com.atlassian.jira.bc.issue.DefaultIssueService.create(DefaultIssueService.java:200)
      4 frames
    3. Java RT
      NativeMethodAccessorImpl.invoke0
      1. sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      1 frame