How to show sub-tasks on Issue screen

Question

I am on Jira Core Cloud.  I have developed an issue type and screen along with a workflow.  I have it almost perfect...  But I cannot see Sub-tasks like in the picture here (which I pulled off of another question on the web).  How do I get the Issue screen to show the sub-tasks of the issue?

John Horst_tncjca · Answer

OK, for the benefit of others, I learned from other posts that Field Configuration (Schemes) really isn't the right place to accomplish what I wanted.  My main concern was enforcing different requirements between the main issue type and the sub task issue type.  That seems to be better done in the workflow transitions where fields can be set as required.

So I have one more complex workflow for the main issue type, and another more simple one for the sub task.

One thing I noticed, though, is that in the Kanban board allows an issue to be created by just entering the summary.  While any transition from that point can enforce field requirements, I did not want the issue to even be created unless certain fields were filled out.  But I did not want the same requirements applied across issue type - except for one field, the Due Date.  So I set that in the Default Field Configuration as Required.  Once I did that, when I went to create an issue on the Board, the create issue screen showed and enforced at least that requirement.

New to all of this so any other comments if I did not quite do this right will be appreciated.

Alexey Matveev · Answer

You can associate a separate field configuration for each issue type. You can find more info here:

https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html

John Horst_tncjca · Answer

I am struggling to associate the subtask with a different field configuration than the parent issue type.  When I am in the Project >> Settings >> Summary, it is showing that my two issue types use the same field configuration...  This is what I do not want.  I want each issue type using its own field configuration.

But it appears I can only associate one field configuration to the project???