Very long string name when creating new Field Configuration or Field Configuration schemes results on Sorry, we had some technical problems pop up

XMLWordPrintable

    • 9.04
    • 1
    • Severity 3 - Minor

      Issue Summary

      This is reproducible on Data Center: yes

      It was tested with Jira 9.12.15 and 10.3 EAP001

      Steps to Reproduce

      1. As admin, create a new Field configuration or Field Configutation scheme under System > Issues > Fields.
      2. Insert a long name as title.

      Expected Results

      Jira should inform a message informing that The name you've entered is too long. You can use up to xx characters

      Actual Results

      A pop up screen show up the error show up instead of a friendly UI message.

       

      Sorry, we had some technical problems during your last operation.

      Request assistance

      1. Collect this information: when the problem occurred, after what operation (if you can)
      2. Collect server logs using log's referral number (below)
      3. Create a Support ZIP
      4. Raise an issue for the Support team providing as much detail as possible, such as when the problem occurred, server logs, Support ZIP and the technical details (below).

        Technical details

      Log's referral number: 7f62dbaa-5a0e-4ab3-ade0-d25f86be20b3

      Cause

      Referer URL: *https://linux-86929.prod.atl-cd.net/jira/secure/admin/ViewFieldScreenSchemes.jspa*

      com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:FieldScreenScheme][name,The name you've entered is too long. You can use up to 60 characters.The name you've entered is too long. You can use up to 60 characters.The name you've entered is too long. You can use up to 60 characters.The name you've entered is too long. You can use up to 60 characters.The name you've entered is too long. You can use up to 60 characters.The name you've entered is too long. You can use up to 60 characters.The name you've entered is too long. You can use up to 60 characters.The name you've entered is too long. You can use up to 60 .
      .
      .
      characters.][description,][id,10100] (SQL Exception while executing the following:INSERT INTO public.fieldscreenscheme (ID, NAME, DESCRIPTION) VALUES (?, ?, ?) (ERROR: value too long for type character varying(255)))
      	at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:211) [entityengine-4.0.1.jar:?]
      	at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:176) [entityengine-4.0.1.jar:?]
      	at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:89) [entityengine-4.0.1.jar:?]
      	at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:566) [entityengine-4.0.1.jar:?]
      	at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:552) [entityengine-4.0.1.jar:?]
      	at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:114) [entityengine-4.0.1.jar:?]
      	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:296) [classes/:?]
      	... 337 more
      Caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO public.fieldscreenscheme (ID, NAME, DESCRIPTION) VALUES (?, ?, ?) (ERROR: value too long for type character varying(255))
      	at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:586) [entityengine-4.0.1.jar:?]
      	at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:203) [entityengine-4.0.1.jar:?]
      	... 343 more
      Caused by: org.postgresql.util.PSQLException: ERROR: value too long for type character varying(255)
      	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2725) [postgresql-42.7.3.jar:42.7.3]
      	at .
      .
      	at com.atlassian.diagnostics.internal.platform.monitor.db.DefaultDatabaseDiagnosticsCollector.recordExecutionTime(DefaultDatabaseDiagnosticsCollector.java:91) [atlassian-diagnostics-platform-5.0.0.jar:?]
      	at com.atlassian.jira.diagnostic.connection.DatabaseDiagnosticsCollectorDelegate.recordExecutionTime(DatabaseDiagnosticsCollectorDelegate.java:62) [classes/:?]
      	at com.atlassian.jira.diagnostic.connection.DiagnosticPreparedStatement.executeUpdate(DiagnosticPreparedStatement.java:69) [classes/:?]
      	at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:578) [entityengine-4.0.1.jar:?]
      	... 344 more 

      Workaround

      Insert a new name with less than 60 characters.

      The UI should be better managed by Jira instead of showing up the error message.

            Assignee:
            Unassigned
            Reporter:
            Rodrigo Bruch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: