Cannot create an issue of a specific issue type in epic

[Florian Schlüter]

For a Jira project I created a custom issue type called "Fristenüberwachung".

When I use the Create button from the main menu at the top, I can create tickets with the type Fristenüberwachung without any problems.

When I try to create a Fristenüberwachung issue within an epic, there is an error message saying that the issue could not be created (see screenshot).

If I choose any other issue type, there is no problem for creating issues from inside an epic.

If I create a Fristenüberwachung issue from outside of an epic, it works fine, and I can associate that issue with an epic afterwards.

Any idea on how to resolve that problem ?

[Martin Bayer _MoroSystems_ s_r_o__ · Accepted solution]

Hi @Florian Schlüter , can you check the workflow for your issue type and it's initial transition? (Transition to your initial status). Do you have some conditions or validators set for it?

[Florian Schlüter]

That is the Workflow used for all issue types in that project 

I didn't set any conditions or validators.

[Martin Bayer _MoroSystems_ s_r_o__]

Hm, that's weird. Can you translate the error message for me, please? :)

[Florian Schlüter]

It translates into:

We couldn't create subordinate issue.

Please check your connection and try again.

And then it proposes to either retry or abort.

[Martin Bayer _MoroSystems_ s_r_o__]

I found one similar issue, but I'm not sure it can be coused in your use case (only one issuetype does not work) - https://jira.atlassian.com/browse/JRACLOUD-73555

But there is another hint. Can you go to developers console in your browser -> Network and check the error response for your create issue request?

[Florian Schlüter]

This is the response to the ajax request when I try to create an issue

[Martin Bayer _MoroSystems_ s_r_o__]

ok, so can you check the create screen for your issue type?

[Florian Schlüter]

@Martin Bayer _MoroSystems_ s_r_o__ 

I got it, I didn't have the "summary" field on the screenmask for the "Fristenüberwachung" issue type.

I now added the "summary" field to it and now it works.

Thanks for your help.