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.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs