Limit sub-tasks to specific issue types

Corey Young

We want to limit the use of sub-tasks to specific issue types. For these specific issue types, the sub task functionality would be available. For the other issue types, the sub task functionality would not be available (and would therefore not appear in the user interface).

Is this possible?

-Corey

Natalie Hobson

I'm adding this as a comment since it's not actually an answer that gives you the requested functionality. Have you thought about using naming convention and communicating this to users? For instance, tell them that they should only create sub-tasks that match the name of the parent. So "Sub-task" for "Task", "Sub-story" for "Story", etc.? I know that's not ideal, but if you aren't able to find a way to code it that could be an alternate way of doing it.