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

More subtle message when adding Resolution name longer than 60 characters

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

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

      The following are thrown in the atlassian-jira.log

      com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Resolution][id,10100][sequence,7][description,][name,Trying to put the resolution name to be longer than 60 characters and see if that will throw an error or something] (SQL Exception while executing the following:INSERT INTO resolution (ID, SEQUENCE, pname, DESCRIPTION, ICONURL) VALUES (?, ?, ?, ?, ?) (Data truncation: Data too long for column 'pname' at row 1))
      	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:393)
      	at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.createValue(WrappingOfBizDelegator.java:206)

      Basically the pname column for resolution table has a limit of 60 characters, which can easily be updated in the database to have it more than 60 characters.

      Instead of showing the following image/page

      It would be nicer to have a warning saying something like the following

      The 'resolution' name is too long. Please enter a shorter name.

      Attachments

        1. error.png
          16 kB
          Zul NS [Atlassian]

        Issue Links

          Activity

            People

              Unassigned Unassigned
              znoorsazali Zul NS [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: