JIRA 4.0 : Enabling Sub-tasks
This page last changed on Oct 01, 2009 by alui.
Sub-task issues are generally used to split up a parent issue into a number of tasks which can be assigned and tracked separately. Sub-tasks have all the same fields as standard issues, although note that their 'issue type' must be one of the sub-task issue types (see below) rather than one of the standard issue types. Once you have enabled sub-tasks and defined at least one sub-task issue type, users will be able to:
On this page: Enabling sub-tasksSub-tasks are disabled by default. To enable sub-tasks:
Defining sub-task issue typesSub-tasks must be assigned one of the sub-task issue types, which are different to standard issue types. Please note that you must define at least one sub-task issue type before users can create sub-tasks. Sub-task issue types can be customised on the 'Sub-Tasks' administration screen (which is described above). The 'Sub-Tasks' administration screen allows you to create, delete, edit, translate and choose icons for your sub-task issue types. For details, please see ' Defining Issue Types '. Configuring sub-tasks and workflowIt is possible to restrict the progression of an issue through workflow depending on the state of the issue's sub-tasks. For example, you might need to restrict an issue from being resolved until all of its sub-tasks are resolved. To achieve this, you would create a custom workflow and use the Sub-Task Blocking Condition on the workflow transitions that are to be restricted by the sub-tasks' state. Configuring sub-task fieldsYou can choose which subtask fields are displayed in the 'Sub-Tasks' section of an issue (see Working with sub-tasks '), i.e.:
This is done via the jira-application.properties file. Disabling sub-tasksSub-tasks are disabled from the sub-task administration screen. To disable sub-tasks please follow the following steps:
|
![]() |
Document generated by Confluence on Oct 06, 2009 00:26 |