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

Error when adding a group with name longer than 60 characters to a notification scheme: too long for database column

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Medium
    • None
    • None
    • Customer: JIRA Enterprise 3.6.5 using PostgreSQL.
      Me: JIRA Standalone Enterprise 3.10.1 using MySQL

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Create a group with a name longer than 60 characters. Then try to add it to a notification scheme. You get the following error (on the screen as well as in the logs):

      org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO notification (ID, SCHEME, 
      EVENT, EVENT_TYPE_ID, TEMPLATE_ID, notif_type, notif_parameter) VALUES (?, ?, ?, ?, ?, ?, ?) (Data truncation: Data too long for 
      column 'notif_parameter' at row 1)
              at org.ofbiz.core.entity.jdbc.SQLProcessor.executeUpdate(SQLProcessor.java:375)
      

      The problem is that the notif_parameter column of the notification table is a varchar(60), and the groupname is stored directly in this field.
      The groupname field of the groupbase table is varchar(255).

      This bug is compounded by the fact that you can't simply change a group name (to reduce it to less than 60 characters).

      A support customer has this issue in 3.6.5 Enterprise running on Postgres. I have reproduced it in 3.10.1 Enterprise running MySQL.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              idaniel Ian Daniel [Atlassian]
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: