New error creating a child issue / We can no longer input required fields before creating

[Julia Sears]

Hi! We use company-managed projects and we require the "team" field for epic and story issue types upon creation. Up until last week, this worked fine across the variety of entry points that Jira Cloud software allows a user to create stories.

Within the last week, we can no longer use the 'add a child issue' or the Plus sign next to child issues while viewing a parent epic to create a story because the 'quick create' view only lets us put the title in. We get an error that reads "We couldn't create the child issue - field team is required."

Previously, when adding a child issue -- Jira Cloud software would open a full create issue screen so that we could input the required fields before it was created. 

Why was this UI changed? We do NOT wish to make the Team field optional as it's critical for our cross-functional projects. We are using the workaround to create stories from the top navigation but our users prefer creating stories within the parent so they don't have to take the extra step of selecting the right parent.

Can Atlassian revert back to the prior flow of:

1. user clicks on add a child issue
2. user write story name
3. software opens larger create issue window so rest of fields can be added
4. user clicks submit

(#3 is getting skipped now!)

[John Cox]

Having the same issue, started ~1 week ago.  Filed a support ticket, waiting for a response.

[John Cox]

First time we observed the issue happening was March 28th.

Maybe of relevance, the field in my project it's erroring out on is required as a function of a Validator on the create step of it's workflow.  The field itself in the field scheme isn't set as required.

In my projects I don't have a similar setup but using an issue required by the field scheme instead of a workflow validator.

[Dave Elger]

I am running into the same issue, I can't quite tell when it started but it seems recent so maybe something changed affecting me and Julia at the same time.  

When using the inline creates "+" or Create Subtask button, with required field validators in place in the Create issue transition, the error pops up and the Create issue screen does not.  This basically makes the inline creation buttons useless.  Creation fails.

Pretty sure the Create issue screen used to show allowing the validation to function properly.

[Sergio]

any solution to this problem?

[John Funk]

Hi Julia - Welcome to the Atlassian Community!

You should enter a support ticket with Atlassian here: https://support.atlassian.com/contact/#/

Please post back here with the resolution. 

Good luck!

[John Funk]

@Julia Sears  @John Cox  @Dave Elger - Did you enter a support ticket? 

[John Cox]

Yes

[John Funk]

Any feedback yet from Support? 

[Julia Sears]

Yes, two things:
1.) There is a known bug tracked here: https://jira.atlassian.com/browse/JRACLOUD-80148    You can add yourself as an affected customer and watcher to track the bug. It suggests two workarounds.

2.) Opening a support case was very helpful. For my instance - the dev team turned off a feature flag that was specifically developed to workaround this bug and it won't affect any other functionality. When the bug is fixed, I am assured everything will work as expected and I don't need to take any actions from my end.

I suggest you open a case and see if they can also turn off a feature flag for you.

[John Cox]

I was pointed to the same issue as Julia and was told it will be rolling out shortly.

[John Funk]

Glad to see it is In Progress and hopefully will be fixed soon. Thanks for opening the support ticket so the fix would be known. 

[Q2 Bookings]

I am having the same issue as well. Can Atlassian please advise when the problem will be corrected