See the Sub-Tasks in Operation

Sub Banner

Once the Sub Task App has been successfully installed and one or more templates have been configured (see Capturing & Maintaining Templates) it is possible to start applying the templates to tickets as follows:

Select a Template for a Ticket and Create the Associated Sub-Tasks

The ticket field drop down identified as the Task Template list during configuration must be visible and available in the ticket form (1).

If a value is selected from the list of templates the Sub Task App is presented in the app tray (2) with an option to create the sub-tasks associated with the template (3).

*NOTE: Although the template can be selected during the creation of a ticket, the option to create the sub-tasks won't be available until after the parent ticket has been submitted.

Navigating to a Sub-Task Ticket

All sub-tasks associated with the chosen template will be created as a separate ticket and displayed in the Sub Tasks side app (1).

Select one of the sub-task name links to navigate to the corresponding ticket (2).

Navigate back to the Parent Ticket

Notice the subject of the sub-task ticket has been constructed form the name of the sub-task taken from the configured drop down and the name of the parent task (1).

The description of the sub-task ticket is taken from the description captured using the Sub Task App configurator (2).

Select the link in the Sub Tasks side app to navigate back to the parent ticket (3).

Monitor Progress against the Sub-Tasks

Notice that as each of the sub-task tickets is solved the associated checkbox is ticked (1) to denote completion and the solved date is recorded (2).

Also notice that until all sub-taks have been completed the option to solve the parent ticket is disabled (3).

However, if any of the sub-tasks are not applicable for the parent ticket it is possible to manually override the completion status (4), thus allowing the parent ticket to be solved.

Selecting this option to override will put the corresponding sub-task ticket into a status of on-Hold and if the checkbox is unticked the sub-task ticket is reopened.

*NOTE: when the parent ticket is solved any sub-task tickets placed in an on hold status due to the manual override will be deleted.

See the Sub-Tasks in Operation

Sub Banner

See the Sub-Tasks in Operation

Once the Sub Task App has been successfully installed and one or more templates have been configured (see Capturing & Maintaining Templates) it is possible to start applying the templates to tickets as follows:

Select a Template for a Ticket and Create the Associated Sub-Tasks

The ticket field drop down identified as the Task Template list during configuration must be visible and available in the ticket form (1).

If a value is selected from the list of templates the Sub Task App is presented in the app tray (2) with an option to create the sub-tasks associated with the template (3).

*NOTE: Although the template can be selected during the creation of a ticket, the option to create the sub-tasks won't be available until after the parent ticket has been submitted.

Navigating to a Sub-Task Ticket

All sub-tasks associated with the chosen template will be created as a separate ticket and displayed in the Sub Tasks side app (1).

Select one of the sub-task name links to navigate to the corresponding ticket (2).

Navigate back to the Parent Ticket

Notice the subject of the sub-task ticket has been constructed form the name of the sub-task taken from the configured drop down and the name of the parent task (1).

The description of the sub-task ticket is taken from the description captured using the Sub Task App configurator (2).

Select the link in the Sub Tasks side app to navigate back to the parent ticket (3).

Monitor Progress against the Sub-Tasks

Notice that as each of the sub-task tickets is solved the associated checkbox is ticked (1) to denote completion and the solved date is recorded (2).

Also notice that until all sub-taks have been completed the option to solve the parent ticket is disabled (3).

However, if any of the sub-tasks are not applicable for the parent ticket it is possible to manually override the completion status (4), thus allowing the parent ticket to be solved.

Selecting this option to override will put the corresponding sub-task ticket into a status of on-Hold and if the checkbox is unticked the sub-task ticket is reopened.

*NOTE: when the parent ticket is solved any sub-task tickets placed in an on hold status due to the manual override will be deleted.

See the Sub-Tasks in Operation

Sub Banner

Once the Sub Task App has been successfully installed and one or more templates have been configured (see Capturing & Maintaining Templates) it is possible to start applying the templates to tickets as follows:

Select a Template for a Ticket and Create the Associated Sub-Tasks

The ticket field drop down identified as the Task Template list during configuration must be visible and available in the ticket form (1).

If a value is selected from the list of templates the Sub Task App is presented in the app tray (2) with an option to create the sub-tasks associated with the template (3).

*NOTE: Although the template can be selected during the creation of a ticket, the option to create the sub-tasks won't be available until after the parent ticket has been submitted.

Navigating to a Sub-Task Ticket

All sub-tasks associated with the chosen template will be created as a separate ticket and displayed in the Sub Tasks side app (1).

Select one of the sub-task name links to navigate to the corresponding ticket (2).

Navigate back to the Parent Ticket

Notice the subject of the sub-task ticket has been constructed form the name of the sub-task taken from the configured drop down and the name of the parent task (1).

The description of the sub-task ticket is taken from the description captured using the Sub Task App configurator (2).

Select the link in the Sub Tasks side app to navigate back to the parent ticket (3).

Monitor Progress against the Sub-Tasks

Notice that as each of the sub-task tickets is solved the associated checkbox is ticked (1) to denote completion and the solved date is recorded (2).

Also notice that until all sub-taks have been completed the option to solve the parent ticket is disabled (3).

However, if any of the sub-tasks are not applicable for the parent ticket it is possible to manually override the completion status (4), thus allowing the parent ticket to be solved.

Selecting this option to override will put the corresponding sub-task ticket into a status of on-Hold and if the checkbox is unticked the sub-task ticket is reopened.

*NOTE: when the parent ticket is solved any sub-task tickets placed in an on hold status due to the manual override will be deleted.

See the Sub-Tasks in Operation

Sub Banner

See the Sub-Tasks in Operation

Once the Sub Task App has been successfully installed and one or more templates have been configured (see Capturing & Maintaining Templates) it is possible to start applying the templates to tickets as follows:

Select a Template for a Ticket and Create the Associated Sub-Tasks

The ticket field drop down identified as the Task Template list during configuration must be visible and available in the ticket form (1).

If a value is selected from the list of templates the Sub Task App is presented in the app tray (2) with an option to create the sub-tasks associated with the template (3).

*NOTE: Although the template can be selected during the creation of a ticket, the option to create the sub-tasks won't be available until after the parent ticket has been submitted.

Navigating to a Sub-Task Ticket

All sub-tasks associated with the chosen template will be created as a separate ticket and displayed in the Sub Tasks side app (1).

Select one of the sub-task name links to navigate to the corresponding ticket (2).

Navigate back to the Parent Ticket

Notice the subject of the sub-task ticket has been constructed form the name of the sub-task taken from the configured drop down and the name of the parent task (1).

The description of the sub-task ticket is taken from the description captured using the Sub Task App configurator (2).

Select the link in the Sub Tasks side app to navigate back to the parent ticket (3).

Monitor Progress against the Sub-Tasks

Notice that as each of the sub-task tickets is solved the associated checkbox is ticked (1) to denote completion and the solved date is recorded (2).

Also notice that until all sub-taks have been completed the option to solve the parent ticket is disabled (3).

However, if any of the sub-tasks are not applicable for the parent ticket it is possible to manually override the completion status (4), thus allowing the parent ticket to be solved.

Selecting this option to override will put the corresponding sub-task ticket into a status of on-Hold and if the checkbox is unticked the sub-task ticket is reopened.

*NOTE: when the parent ticket is solved any sub-task tickets placed in an on hold status due to the manual override will be deleted.