Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-75683

Jira displays generic error message instead of error specified in workflow validator settings

XMLWordPrintable

      Issue Summary

      When creating a ticket that uses a 'Field has been modified Validator' on the description field, Jira does not display the error message specified in the validator settings when using the inline issue creation inside of an Epic.

      This behaviour is also reproducible on the 'Field Required Validator'.

      Steps to Reproduce

      1. Create a new validator on a workflow step using the FIeld has been modified Validator
      2. Make sure you have specified an error message
      3. Attempt to create a new ticket issue inside of an Epic, using the plus sign "+" next to Issues in this epic

      Expected Results

      Jira should display the error that you provided in the validator settings

      Actual Results

      Jira shows the following message when creating issues inside an epic:

      We couldn't create the child issue
      Check your connection, then give it another try

      Workaround

      1. Create new issues using the "Create" button in the top navigation bar and add this to the epic later, or
      2. Remove the field required validator

        1. Screen Shot 2020-12-07 at 4.55.29 PM.png
          Screen Shot 2020-12-07 at 4.55.29 PM.png
          136 kB

            [JRACLOUD-75683] Jira displays generic error message instead of error specified in workflow validator settings

            Matthew Hunter added a comment -
            Atlassian Update - January 18, 2023

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - January 18, 2023 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              htemp Heitor T (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: