nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't create issue in epic. Error message falsely says "Description required"

Andrea Kunkel

I'm trying to create a new issue in an epic but I get an error message saying:

"We couldn't create the child issue
Description required"

jira create issue error.png

I checked the settings and the field Description is NOT set to required so there should not be an error.

What's even more confusing is that I don't get an error in another project. There I can just create a new issue without a description.

Any ideas would else I could try?
As mentioned above I checked the Field Configuration and even tried to make it Required and change it back to Optional which didn't solve it.

Btw, I also realised that on the standard Create issue Screen the Description doesn't show as required (no *) but when I want to create it the same error shows (Description required).

I know a related bug has already been raised but I don't think that's the issue here because there is no required field in my configuration.
https://jira.atlassian.com/browse/JRACLOUD-75648

Accepted answers

All comments

Nic Brough -Adaptavist-

Can you be entirely sure that the "create issue in Epic" is leading to creating an issue of the same type in the same project as the one you have tested the plain create for?

Andrea Kunkel

I already found the solution yesterday, I think there was a workflow set up somewhere that required the description to not be empty. I don't really remember where that was as the Jira settings are very confusing with all these different schemes.

I tried to delete this question last night but couldn't find it anywhere. Is there a way to close this without accepting your answer?

Nic Brough -Adaptavist-

We don't delete questions here when answered - the Community acts as a knowledge-base in some ways (if you were to look at my profile, you'd see I've answered a few more questions than I have asked over the years - 16 I think. It's because I've been able to find the answers here on questions other people have asked, and so I've not needed to ask again!)

My answer is not the right one for you, but you've found the right one. The best way to "close" this question is for

1. You to post your solution as an answer

2. I can accept the answer

You could accept your own answer, but you don't get kudos/points for that. You do if I accept it for you!

We do remove questions if posters really want us to, so let me know if that is the case, but I'd like to keep your answer here, marked right, so other people can learn from you.

Andrea Kunkel

I found the answer:

We have a workflow in this project where a validator was set that didn't let you create an issue without a description.

I removed this validator and now it's working.

Where did I find this:
Project settings -> Workflows -> Edit -> Diagram -> Create -> Validators

Andrea Kunkel

Thanks a lot for explaining.
I couldn't find the question after I submitted it so I thought it might not have been published yet and I could delete it before it showed. No need to delete it now that it has some comments/reactions.

I added a new answer with the solution. Feel free to accept it for me.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud