Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-36799

More subtle message when adding Resolution name longer than 60 characters

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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

        Issue Links

          is related to

          Suggestion - JRASERVER-36799 More subtle message when adding Resolution name longer than 60 characters

          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: