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

Unspecific message shown in Portal when a validation in "Create Issue" transition fails

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 4.10.0
    • 3.13.0, 3.16.1
    • Customer Portal
    • None

      Summary

      When administrator adds an additional validator to the "Create" transition and user tried to create an issue (which is using the workflow with the additional validator) from Customer portal, the issue creation will fail with following error if user did not fulfill the validator:

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

      Steps to reproduce

      1. Edit the existing workflow used by a Service Desk project.
      2. Add a validator (Eg: "Field Required" from JSU) to the "Create" transition.
      3. Publish the workflow.
      4. Try creating issue from Service Desk portal.

      Environment

      Jira Service Desk 3.16.0, 3.16.1

      Expected Results

      Issue creation failed by specifying field which is failed the validation.

      Actual Results

      Following error shown in Customer Portal:

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

      Workaround

      Remove the validator that requires the field on Create Issue transition on the workflow.

            [JSDSERVER-6257] Unspecific message shown in Portal when a validation in "Create Issue" transition fails

            Burak Kaya added a comment -

            ++

            Burak Kaya added a comment - ++

            Paula Manildi added a comment - - edited

            We see this as well - we added a watcher in a post function  to the create transition and now see this issue. JSD 3.15.3

            However, have since identified that the post function must be AFTER the initial create. https://community.atlassian.com/t5/Jira-questions/We-can-t-create-this-issue-for-you-right-now-it-could-be-due-to/qaq-p/83478

            So, no longer an issie.

            Paula Manildi added a comment - - edited We see this as well - we added a watcher in a post function  to the create transition and now see this issue. JSD 3.15.3 However, have since identified that the post function must be AFTER the initial create.  https://community.atlassian.com/t5/Jira-questions/We-can-t-create-this-issue-for-you-right-now-it-could-be-due-to/qaq-p/83478 So, no longer an issie.

            Minor? This is a customer-faced bug!

            Denis Zvonov added a comment - Minor? This is a customer-faced bug!

            Savannah Ritter added a comment - - edited

            Still an issue on JSD Server 4.5.1. We only just discovered this stopped working with a recent update, which caused confusion for users mysteriously not being able to submit tickets since the error is unclear. Not using validators on JSD create at all is not an acceptable workaround.

            This is the kind of problem that make us want to ditch Service Desk entirely - we can't rely on standard Jira functionality to work in it consistently

            Savannah Ritter added a comment - - edited Still an issue on JSD Server 4.5.1. We only just discovered this stopped working with a recent update, which caused confusion for users mysteriously not being able to submit tickets since the error is unclear. Not using validators on JSD create at all is not an acceptable workaround. This is the kind of problem that make us want to ditch Service Desk entirely - we can't rely on standard Jira functionality to work in it consistently

            Same issue here, JSD Server 4.3.4 Only 1 validator set (create issues permission)

            Dave Mathijs added a comment - Same issue here, JSD Server 4.3.4 Only 1 validator set (create issues permission)

            Peter Pesta added a comment - - edited

            Hi Guys,
            Our client experience this issue even with only one default "create issues" permission validator is set. The issues are created though, even if the error message appears. Any ideas how to fix that?

             

            JSD Server version: 4.5.0

            Peter Pesta added a comment - - edited Hi Guys, Our client experience this issue even with only one default "create issues" permission validator is set. The issues are created though, even if the error message appears. Any ideas how to fix that?   JSD Server version: 4.5.0

            Steven P added a comment - - edited

            I wouldn't mind this so much if it didn't have a better error message already in Jira Service Desk 3.8.1 and so lost the better alert in favour of a worse alert..

             

            e.g. if Summary wasn't filled out it in 3.8.1 then directly under Summary is red text that says "Please provide a valid value for field 'Summary'"  It's great!  Clear, points you to the error and while it could be even better (by suggesting possible values: numbers, vs text etc.) it's still way better than the generic "We were unable to submit your request. "

            Steven P added a comment - - edited I wouldn't mind this so much if it didn't have a better error message already in Jira Service Desk 3.8.1 and so lost the better alert in favour of a worse alert..   e.g. if Summary wasn't filled out it in 3.8.1 then directly under Summary is red text that says "Please provide a valid value for field 'Summary'"  It's great!  Clear, points you to the error and while it could be even better (by suggesting possible values: numbers, vs text etc.) it's still way better than the generic "We were unable to submit your request. "

            Hi,

            In which Jira service desk version this issue is planned to be fixed

            Thanks,

            Mohamed El Taweel added a comment - Hi, In which Jira service desk version this issue is planned to be fixed Thanks,

            Remainder !!

            Can you please check and update on below.

            Hi, This worked on couple of months back. it got stopped somehow. Not sure, either any upgrade done on JSU plugin that causes the issue. 

            Harish Tirumalasetty added a comment - Remainder !! Can you please check and update on below. Hi, This worked on couple of months back. it got stopped somehow. Not sure, either any upgrade done on JSU plugin that causes the issue. 

            Hi, This worked on couple of months back. it got stopped somehow. Not sure, either any upgrade done on JSU plugin that causes the issue. 

            syed ashraf alam added a comment - Hi, This worked on couple of months back. it got stopped somehow. Not sure, either any upgrade done on JSU plugin that causes the issue. 

              14858f4147da Nafis Faramarzi
              vshanmugam Vicknesh Shanmugam (Inactive)
              Affected customers:
              38 This affects my team
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: