JIRA displays generic error message instead of error specified in workflow validator settings

XMLWordPrintable

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

      Summary

      When creating a ticket that uses a 'Field has been modified Validator' on the description field, JIRA does not display the error message specified in the validator settings

      Environment

      Cloud JIRA v1000.73.0

      Steps to Reproduce

      1. Create a new validator on a workflow step using the FIeld has been modified Validator
      2. Make sure you have specified an error message
      3. Attempt to create a new ticket leaving the field you specified for the validator empty

      Expected Results

      JIRA should display the error that you provided in the validator settings

      Actual Results

      JIRA displays a generic error message stating:

      We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persist, contact your administrator as they'll be able to access more specific information in the log file.

      Notes

      The error message specified in the validator settings appears to get logged in the JIRA log

      2016-06-20 10:14:12.032962500 Caused by: com.opensymphony.workflow.WorkflowException: This field is required.
      

      This also appears to effect the 'Field Required Validator' validator as well.

      Workaround

      Remove the validator from the field or create custom fields for this project and mark them as required.
      Customers can use the 'Field must not be empty during the transition.' validator as well.

      Additional information

      This appears to be affecting post functions as well with the same generic error being displayed

            Assignee:
            Unassigned
            Reporter:
            mlavender (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: