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.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot