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

Cannot create child issue from Epic in new issue view when there is required field

      Summary

      with the New Issue View enabled if there are any required fields configured for an issue type when attempting to use the quick create option under the issues in Epic panel in the View screen of an epic you will encounter the error "We couldn't create the child issue Check your connection, then give it another try"

      Environment

      • Jira Cloud with New issue view enabled

      Steps to Reproduce

      1. enable the New issue View
      2. Set any field to required that is on the field scheme for a standard issue type on the desired project
        • where that required field is not in the Create screen of the issue type in question
      3. navigate to an Epic
      4. use the quick create "+" sign in the issues in Epic panel to create an issue

      Expected Results

      If there are required fields, a popup occurs allowing a user to enter the additional required field data points,

      Actual Results

      Only the Summary is allowed to be entered from this location and you encounter the error:

      We couldn't create the child issue

      Check your connection, then give it another try

      Workaround

      The following Workaround is only available until Mar 31, 2021 noting:

      From Mar 31, 2021, we'll be moving all users on the old issue view in Jira Cloud products (Jira Software, Jira Service Management, Jira Core) to the new issue view — which means you won't be able to switch back to the old view anymore. For key dates, what's next, and more details, check out our official announcement.

      Disable the New issue view by navigating to your user icon in the upper right of the screen, and selecting "Personal settings" then scroll down to the "Atlassian Labs" section and deselect the green selector slider for the new issue view:

      With the new issue view disabled you will be able to use the quick create option from the issues in the epic panel

          Form Name

            [JRACLOUD-75648] Cannot create child issue from Epic in new issue view when there is required field

            Hey bf33a2d2690e if you are experiencing this behaviour we recommend creating a Support Ticket with us as this particular bug was closed as Fixed. Thank you!

            Anusha Rutnam added a comment - Hey bf33a2d2690e if you are experiencing this behaviour we recommend creating a Support Ticket with us as this particular bug was closed as Fixed. Thank you!

            This is happening in Edge, but not in Chrome.  Just started when we enabled the new Issue View site wide last week.

             

            Scottie Brimmer added a comment - This is happening in Edge, but not in Chrome.  Just started when we enabled the new Issue View site wide last week.  

            dddd9fc336d2 and bdd74cae8db3, I did a quick test and set a field as required in the Field configuration and when trying to create a child issue in an Epic, the Issue creation dialog appeared as expected. If this is not the behavior you are receiving, your scenario might be different, and what I recommend is raising a support request for this so our Atlassian Support team can look into it. You can raise it here: https://support.atlassian.com/contact/#/

            Rene C. [Atlassian Support] added a comment - dddd9fc336d2 and bdd74cae8db3 , I did a quick test and set a field as required in the Field configuration and when trying to create a child issue in an Epic, the Issue creation dialog appeared as expected. If this is not the behavior you are receiving, your scenario might be different, and what I recommend is raising a support request for this so our Atlassian Support team can look into it. You can raise it here: https://support.atlassian.com/contact/#/

            rneill19 added a comment -

            This issue is still happening - are there any updates?

            rneill19 added a comment - This issue is still happening - are there any updates?

            This is still an issue.  Please review

            Todd Winton added a comment - This is still an issue.  Please review

            poff added a comment -

            This issue still affects my team.  Can you please share resolution details/expected release date?  Thank you! 

            poff added a comment - This issue still affects my team.  Can you please share resolution details/expected release date?  Thank you! 

            Allen Tong added a comment -

            Someone needs to contact Jira team and let them know this is still not fixed

            Allen Tong added a comment - Someone needs to contact Jira team and let them know this is still not fixed

            Karri Adkins added a comment - - edited

            I am lost, it says it is fixed, but where?  When did it go out?  What was fixed exactly? There is nothing in this ticket that explains if it was fixed besides the resolution, where is the validation detail?......a little frustrating.

            Karri Adkins added a comment - - edited I am lost, it says it is fixed, but where?  When did it go out?  What was fixed exactly? There is nothing in this ticket that explains if it was fixed besides the resolution, where is the validation detail?......a little frustrating.

            Hello!
            The bug still persists. Has the patch gone up to production yet?

            Ana Paula Santana Campos added a comment - Hello! The bug still persists. Has the patch gone up to production yet?

            agree. When we can use that in the Jira Production? 

            andriy.seniv added a comment - agree. When we can use that in the Jira Production? 

              8120ea81a5c1 Pushyami Gali
              emccutcheon Earl McCutcheon
              Affected customers:
              46 This affects my team
              Watchers:
              69 Start watching this issue

                Created:
                Updated:
                Resolved: