Is there a configuration in a custom issue-type that allows that issue-type to have child issues?

[David Calabrese]

A custom issue-type has been created and I'm looking to see if there is some configuration that allows that issue-type to be the parent of user stories and tasks,  similar to how an epic can be a parent of user stories and tasks. In other words - the ability to spin off child issues from a custom issue-type. 

[Mikael Sandberg]

It can be done, but you need to be on Jira Software Premium plan, which gives you access to issue hierarchy above the default Epics - standard issue types (story & task etc) - sub-task.

Or you could use JXL from the Marketplace which also allows you to configure your own hierarchy.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

No, it's not done at that level.  The hierarchy is spread across the project level, Jira Software, and in  Advanced Roadmaps settings if you have that.

Jira has two layers in the core.  A project can be set up to have many different issue types, but they are of two types - base and sub-task.  You don't enable a base level issue type to have sub-tasks, you tell a project that it has one or more sub-task types, which then enables all the base level issues in the project to have sub-tasks.

Jira Software adds a layer above - Epics can contain base level issues (and across projects, unlike issue/sub-task).

Advanced Roadmaps allows you to go higher - both having more than one issue type at the Epic level, and allowing you to flag others as layers above Epic.

[Shelley Cowan]

How do you tell the project that it has one or more sub-task types to enable all base level issues in the project to have sub-task?  I added a customer issue type to the Epic level in the hierarchy, but it is not behaving the same as the Epic issue type - it is not allowing Child records to be created, only Linked Issues

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

You don't enable a base level issue type to have sub-tasks, you tell a project that it has one or more sub-task types, which then enables all the base level issues in the project to have sub-tasks

Epics are different, they currently represent their child issues by a link.