So far as I know this can't be done OOTB. What we did was to disable the 'Sub-Tasks' modules in the Issue Operations system-plugin, and then (via our own plugin) added web-items to create buttons on the View Issue screen that would allow a user to raise a sub-task of a specific type.
<web-item key="addnewfeaturetesttask" name="New Feature Test Task" section="operations-top-level" weight="10"> <label>Add Test Task</label> <context-provider class="com.ciboodle.jira.plugins.AddNewFeatureTestTaskLinkProvider" /> <link linkId="addnewfeaturetesttask_link">/secure/CreateSubTaskIssue.jspa?parentIssueId=$issue.id&amp;pid=$pid&amp;issuetype=$issueTypeId</link> <condition class="com.ciboodle.jira.plugins.IssueAllowsSubTasks" /> </web-item>
The class IssueAllowsSubTasks checks the type of the issue being viewed, as we only allow certain types of issue to have this type of sub-task; the AddNewFeatureTestTaskLinkProvider class sets up $pid and $issueTypeId for the link-generator.
The net result is that users cannot create sub-tasks except for via this link, and can then only create a sub-task of a specific type - in this case, 'New Feature Test Task'.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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