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

Customer Portal Does Not Display Custom Validator Error

XMLWordPrintable

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

    • Hide

      Hello everyone,

      Thank you for sharing your feedback on this ticket. We acknowledge that we need to make this experience better on Portal. However, we are unable to prioritize this request at the moment, as we are working on other competing priorities.

      We will revisit this again in the next few months. We regret the inconvenience.

      Regards,
      Sushant Koshy
      Product Manager, Jira Service Management

      Show
      Hello everyone, Thank you for sharing your feedback on this ticket. We acknowledge that we need to make this experience better on Portal. However, we are unable to prioritize this request at the moment, as we are working on other competing priorities. We will revisit this again in the next few months. We regret the inconvenience. Regards, Sushant Koshy Product Manager, Jira Service Management

      Summary

      Customers who have configured a Workflow Validator in their Service Desk Projects have noticed that the Custom Validator Error message does not appear in the Customer Portal (if the Validator fails).

      In this scenario, the validator is to ensure that Customer Requests are shared with the Customer's Organizations and are not Private

      Environment

      • Cloud

      How to Reproduce

      Prerequisites

      1. Update and Publish a Service Desk workflow so that a Customer Transition has a Validator (in this example, add a Validator on the Create Transition where the Organization Field must be set and a Custom Error Message if not set)
      2. Create and Add Customer Accounts in a Service Desk Customer Organization

      Steps to Take

      1. As an Agent/Customer, go to the Customer Portal and create a Request where the "Organization" field is set to "Private Request"

      Expected Results

      Error message displays the Custom Error message that is configured in the Validator

      Actual Results

      Issue is not created and the following error is displayed:

      Error

      Your request could not be created. Please check the fields have been correctly filled in.

      Notes

      If the Issue is created in Jira, the error that's displayed matches what is configured in the Workflow Validator:

      Note that Organization is not a field that can be edited on a Create/Edit Issue screen: Feature Request here: https://jira.atlassian.com/browse/JSDCLOUD-4723

      Something like Setting the Organization by Default (https://jira.atlassian.com/browse/JSDCLOUD-5307) may help with this scenario

      Workaround

      No workaround available to set the Organization Field nor alert the Customer that this field must be set during the Creation of the Request

      An Automation rule could be created to send out an Alert to specific Agents if the Request was created without an organization being set

        1. CreateInJira.png
          CreateInJira.png
          63 kB
        2. PortalError.png
          PortalError.png
          66 kB
        3. WorkflowValidator.png
          WorkflowValidator.png
          112 kB

              d0d1ba410583 Sushant Koshy
              scranford Shawn C
              Votes:
              209 Vote for this issue
              Watchers:
              119 Start watching this issue

                Created:
                Updated: