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

Workflow Validator custom error messages Not seen on customer portal

    • We collect Jira Service Desk 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.

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

      when validators are used at create stage of workflow. On service desk customer portal,Though validators are working, we are not able to get the customized validator error message on the screen, instead it shows that error in workflow initialization.
      Is there anyway we can achieve this in service desk 2.3 or in upcoming versions?

            [JSDSERVER-1638] Workflow Validator custom error messages Not seen on customer portal

            We have a validator set in a Jira workflow upon creation. This validator works when trying to create the ticket in Jira. However, when I test creating a ticket in the Jira Service Desk portal, where the customers would be submitting from, the validator stops the creation but only with a generic message instead of the custom message set in the validator in the workflow. It is important our message appears so they know what they are supposed to fix. 

            Michelle Vincent added a comment - We have a validator set in a Jira workflow upon creation. This validator works when trying to create the ticket in Jira. However, when I test creating a ticket in the Jira Service Desk portal, where the customers would be submitting from, the validator stops the creation but only with a generic message instead of the custom message set in the validator in the workflow. It is important our message appears so they know what they are supposed to fix. 

            Even if issues created through the portal show additional information in the error message that is not shown when issues are created through JIRA GUI, like administrator's contact information, I think that validators custom message should be included.

            Fidel Castro added a comment - Even if issues created through the portal show additional information in the error message that is not shown when issues are created through JIRA GUI, like administrator's contact information, I think that validators custom message should be included.

            We are using Service desk 3.0.10 and it is still a problem. We turn on fields validator and it just fails to submit the ticket and just sits there. No error message shows up to the user.

            Chris Whitten [Comskil] added a comment - We are using Service desk 3.0.10 and it is still a problem. We turn on fields validator and it just fails to submit the ticket and just sits there. No error message shows up to the user.

            Patrick van der Rijst added a comment - - edited

            -JSD 2.5.9 here, doesn't work. Trying this within JSD: https://answers.atlassian.com/questions/133658/how-do-i-make-the-second-field-of-a-cascading-select-field-required-

            Don't link the error message to a specific field. Suggestion is still valid, make sure the error message is shown to the field it belongs to.

            Patrick van der Rijst added a comment - - edited -JSD 2.5.9 here, doesn't work. Trying this within JSD: https://answers.atlassian.com/questions/133658/how-do-i-make-the-second-field-of-a-cascading-select-field-required- Don't link the error message to a specific field. Suggestion is still valid, make sure the error message is shown to the field it belongs to.

            It's working fine in jira service desk 2.3

            Mahesh Dubey added a comment - It's working fine in jira service desk 2.3

              Unassigned Unassigned
              5a24e453eb10 Mahesh Dubey
              Votes:
              4 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: