You don't.
Sub-tasks are the same as the parent level issue types - they're all just issue types. If you add 10 issue types into a project's "issue type scheme", all 10 types become available in the project. For the sub-task types, the parent type is irrelevant.
Let's say you have a scheme that says
Tech-task and thing-to-do are available to be added to tasks, stories and issues automatically, because they're in the project. If you want to add a "decision" sub-task, you don't "associate" anything, just add it to the scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.