Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29410

JIRA Throw a Validation Error "Maximum value allowed is 100000000000000" When Number Field is Filled With Larger Number

XMLWordPrintable

    • 4.04
    • Severity 3 - Minor
    • 1
    • Hide
      Atlassian Update – 06 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      Steps to reproduce:

      1. create a Number Field
      2. create an issue and fill in the Number Field with "1000000000000000" (16 digits) , JIRA will throws error as shown in the screenshot NumberField.png

      in the logs for JIRA connecting to Oracle:

      org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:CustomFieldValue][id,1011261]
[issue,54421][numbervalue,1.0E14][parentkey,null][customfield,12256] (SQL Exception while executing the following:
INSERT INTO customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, 
VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) 
(ORA-01438: value larger than specified precision allowed for this column ))

      The entitymodel.xml indicate that the numbervalue is "floating point". refer to screenshot EntityModel.xml
      The fieldtype-*.xml has floating point configured to DECIMAL(18,6). refer to screenshot FieldType.png

        1. EntityModel.png
          EntityModel.png
          4 kB
        2. FieldType.png
          FieldType.png
          10 kB
        3. NumberField.png
          NumberField.png
          35 kB
        4. ATL_SUP_Edit_1.PNG
          ATL_SUP_Edit_1.PNG
          167 kB
        5. ATL_SUP_Edit_2.PNG
          ATL_SUP_Edit_2.PNG
          144 kB
        6. ATL_SUP_Edit_3.PNG
          ATL_SUP_Edit_3.PNG
          170 kB

              Unassigned Unassigned
              jalbion Janet Albion (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: