JIRA

Install

Admin

Use

	JIRA Administrator's Guide Introduction Getting Help Look and Feel Logo, Colours and Timezone Configuring the default Language Configuring the default Issue Navigator Configuring the default Dashboard Overview of Dashboard Portlets Enabling Portlets and Other Plugins Editing the Announcement Banner Enabling Logout Confirmation Email Email Overview Creating a Notification Scheme Customising Email Content Creating Issues & Comments from Email SMTP configuration User Management Managing Users Managing Groups Managing Project Roles Migrating from Groups to Project Roles Enabling public signup and CAPTCHA Integrating JIRA with LDAP Integrating JIRA with Crowd Configuring Trusted Applications Security Overview Global permissions Project permissions Issue security Project Management Defining a Project Assigning members to Project Roles Defining Project Components Defining Project Versions Creating Release Notes for a Version Configuring Project Keys Configuring Fields and Screens Overview Defining 'Resolution' field values Defining 'Priority' field values Defining 'Status' field values Defining 'Issue Type' field values Associating Issue Types with Projects Translating Resolution/Priority/Status/Type Configuring field behaviour Configuring rich-text renderers Associating behaviour with Issue Types Placing fields on screens Associating screens with Issue Operations Associating screens with Issue Types Creating & configuring Custom Fields Custom Field Overview Adding Custom Fields Configuring Custom Fields Configuring Workflow Workflow Activating Workflow Events Importing from Other Systems Importing from Bugzilla Importing from Mantis Importing from FogBugz Importing from Excel/CSV Moving or Archiving Individual Projects Overview Archiving a project Merging JIRA instances Splitting JIRA instances Integrating with Source Control Integrating with CVS and ViewCVS Integrating with Subversion Integrating with Perforce Integrating with ClearCase Integrating with FishEye Configuration Options & Settings Global Settings Enabling Issue Linking Enabling Sub-tasks Enabling sub-tasks Defining sub-task issue t.. Configuring sub-tasks and.. Configuring sub-task fiel.. Disabling sub-tasks Enabling Trackback linking Enabling Time Tracking Enabling File Attachments Enabling Thumbnails for Attachments Server Administration Indexing & Search Backing up Data Automated Backups Restoring Data Database Integrity Checker Increasing memory Performance Tips Database Indexing Precompile JSP pages Logging and Profiling Thread Dump Downgrading (Ent to Pro) Downgrading (Ent to Std) Downgrading (Pro to Std) Using robots.txt with Search Engines Appendix A - Extending JIRA Extension Overview Listeners Services Jelly tags JIRA Toolkit Customising Text Developer Guides JIRA Plugins JIRA RPC Overview Creating a SOAP Client Creating an XML-RPC Client Creating Custom Field Types Custom Workflow Elements Creating new Portlets Creating new Reports More.. JIRA Source Building JIRA from source API Documentation

Enabling and Configuring Sub-tasks

PDF

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:

create sub-tasks.
convert issues to sub-tasks (and vice versa).

Note

Sub-tasks are only supported in the Professional and Enterprise editions of JIRA.

Enabling sub-tasks

Sub-tasks are disabled by default. To enable sub-tasks:

Log in as a user with the 'JIRA Administrators' global permission.
Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard:
Locate the 'Global Settings' sub-menu on the left hand side of the screen, and choose Sub-Tasks from the list.
The 'Sub-Tasks' administration screen will be displayed. Click the 'Enable' link.
The page will reload and inform you that the sub-tasks are now enabled. A default sub-task issue type has also been automatically created. You can edit it by selecting the Edit link in the Operations column.

Defining sub-task issue types

Sub-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 workflow

It 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 fields

You can choose which subtask fields are displayed in the 'Sub-Tasks' section of an issue (see Working with sub-tasks'):

the parent's 'View Issue' screen.
the sub-task 'Quick Create' form.

This is done via the jira-application.properties file.

Disabling sub-tasks

Sub-tasks are disabled from the sub-task administration screen. To disable sub-tasks please follow the following steps:

Log in as a user with the 'JIRA Administrators' global permission.
Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard:
Open the Global Settings sub-menu on the left hand side if it is not open already, and choose Sub-Tasks from the list.
After the Sub-Tasks administration screen loads please click the "Disable" link. The page should reload and inform you that the sub-tasks are now disabled.

Note

Sub-tasks cannot be disabled if one or more sub-tasks exist in the system. You will need to remove the existing sub-tasks (or convert them to standard issues) before disabling this feature.