Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-1638

Workflow Validator custom error messages Not seen on customer portal

XMLWordPrintable

    • 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.

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

        1. image-2018-03-26-13-45-30-491.png
          793 kB

          Form Name

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

            Victor Silva | Stone added a comment -

            Same issue here. This should be open.

            Victor Silva | Stone added a comment - Same issue here. This should be open.

            Deleted Account (Inactive) added a comment - - edited

            I agree, this is not fixed, I get an error that all fields are not filled in properly, disregards what Validator I use and if I configure some error message or not...

            image-2018-03-26-13-45-30-491.pngI

            Deleted Account (Inactive) added a comment - - edited I agree, this is not fixed, I get an error that all fields are not filled in properly, disregards what Validator I use and if I configure some error message or not... image-2018-03-26-13-45-30-491.png I

            David Fischer added a comment -

            In what possible way can this be considered fixed?

            I added Validators to the Create transition, and they all trigger the same error message when customers create an issue from the SD portal:

            No indication of the field, nor the exact error.

            I tested this on the latest JSD Cloud, and I believe the same error exists in JSD Server.

            David Fischer added a comment - In what possible way can this be considered fixed? I added Validators to the Create transition, and they all trigger the same error message when customers create an issue from the SD portal: No indication of the field, nor the exact error. I tested this on the latest JSD Cloud, and I believe the same error exists in JSD Server.

            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.

            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.

            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.

            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.

            Mahesh Dubey added a comment -

            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: