Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3592

Workflow validators result in error when using name

XMLWordPrintable

      Using a workflow validator and using the name in the exception results in an error in the attached screenshot:

      throw new com.opensymphony.workflow.InvalidInputException("summary", "Summary is incorrect")

      The expectation is that the error message will be displayed next to the summary field.

      The following will not work:

      throw new InvalidInputException("summary", "Summary is incorrect")

      But the following will work although not by the field:

      throw new InvalidInputException("Summary is incorrect")

        1. The Bad Error Message.png
          The Bad Error Message.png
          82 kB
        2. The Slightly Better Error Message.png
          The Slightly Better Error Message.png
          37 kB
        3. validator_fails.png
          validator_fails.png
          44 kB

          Form Name

            [JSDSERVER-3592] Workflow validators result in error when using name

            Payne added a comment -

            As Jonny Carter pointed out on 4/19/18, a similar bug is now present; I'm encountering it in JSD Server 3.15.1, just as he describes.

            Payne added a comment - As Jonny Carter pointed out on 4/19/18, a similar bug is now present; I'm encountering it in JSD Server 3.15.1, just as he describes.

            Jonny Carter added a comment -

            There seems to be a regression of a worser kind in 3.10.2 (and possibly other versions). 

            So, if your validator just throws a plain old exception with no field specified, you get a super generic error in the service desk portal that doesn't contain your custom message:

            throw new InvalidInputException("Summary is incorrect")

             

            If you do go to the trouble of specifying a field, you get the same generic exception plus your custom message (with no indication of the field):

            throw new InvalidInputException(com.atlassian.jira.issue.IssueFieldConstants.COMPONENTS, "Summary is incorrect")

             

            Jonny Carter added a comment - There seems to be a regression of a worser kind in 3.10.2 (and possibly other versions).  So, if your validator just throws a plain old exception with no field specified, you get a super generic error in the service desk portal that doesn't contain your custom message: throw new InvalidInputException( "Summary is incorrect" )   If you do go to the trouble of specifying a field, you get the same generic exception  plus your custom message (with no indication of the field): throw new InvalidInputException(com.atlassian.jira.issue.IssueFieldConstants.COMPONENTS, "Summary is incorrect" )  

            pat (Inactive) added a comment -

            Hi cateapage924682711,

            This bug has been fixed in JIRA Service Desk version 3.1.8, you will need to upgrade to get the fix. Hope this helps.

            Pat

            pat (Inactive) added a comment - Hi cateapage924682711 , This bug has been fixed in JIRA Service Desk version 3.1.8, you will need to upgrade to get the fix . Hope this helps. Pat

            Cate Page added a comment -

            Hi, I am receiving this error when I try to log a ticket in my company Helpdesk - JIRA version v7.1.0 Helpdesk version 3.1.0

            could you please advise,

             

            Cate

             

            Cate Page added a comment - Hi, I am receiving this error when I try to log a ticket in my company Helpdesk - JIRA version v7.1.0 Helpdesk version 3.1.0 could you please advise,   Cate  

            angel added a comment -

            Is this fix covering also JSD-3647 on JSD server?

            angel added a comment - Is this fix covering also JSD-3647 on JSD server?

            Jason Dopson added a comment -

            I'm still experiencing this error in JIRA Core 7.1.7/Software 7.1.7/JSD 3.1.7 using the code above.

            Jason Dopson added a comment - I'm still experiencing this error in JIRA Core 7.1.7/Software 7.1.7/JSD 3.1.7 using the code above.

              pteen pat (Inactive)
              4c1113d0d9eb adammarkham
              Affected customers:
              1 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: