Buy Now

STM for Jira Cloud

Sub Tasks, Linked issue, and Epic Issues are a common method for breaking up the work involved in a JIRA Issue.  STM

Templates can either be created for a specific project or globally (for all projects or workflow post functions).  These can then be used in multiple Sub Tasks / Linked Issues / Epic Issues by simply selecting a pre-defined template (you can optionally change a few values if you wish).


You can also create sub tasks automatically as part of the workflow by adding in one of the STMs post function and selecting the global template you want to use (see below for more details).


Important: The fields that are displayed and the fields that can be copied from the parent are dependent on having been set up for the Create Issue screen in the project (Project Administration -> Screens -> Create Issue).  If, for example, the due date is not in the Create Issues screen then it will not appear as an entry field, as a show field checkbox or as a copy from parent checkbox.


Warning: Creating issues during workflow post functions is incredibly powerful.  You need to be careful that you don't set up loops.


New Features:

  1. Cascading Templates allow you to create templates in sequence.  Choose the advanced feature set and at the bottom of the template, you can select one or more templates to create after this one.

  2. Global Executors to create issues automatically for one or more projects.

  3. Executors to easily create issues automatically.  Executors are easy to set up, modify and disable without having to edit workflows.

  4. Who and when a template was changed is now audited and can be viewed in the admin section

  5. In the Reporter and Assignee fields you can now enter ${Reporter} or ${Assignee} to specify the reporter or assignee from the parent (when creating a new issue) or from the current issue (when updating).

  6. You can now create Sub Task, Linked Issues or Epic Issues for a list of issues in the issue filter (including results of JQL search).  See Bulk Update of Issues from an Issue filter.





Defining Templates for Sub Tasks/Linked Issues/Epic Issues

For this section whenever Sub Tasks is mentioned the same will also apply for Epic or Linked Issues.  


Templates for Sub Task are defined either globally for an individual project.


Project Templates

Templates for Sub Tasks are defined for each Project.  The Sub Task Templates screen is available as a Project tab and can be accessed by Project Admins only or those users defined in the Project Template Access group list in the configuration screen.  You can get to the page by going to the general Project pages, Add-ons and then STM Templates


The image below shows the page where templates can be added and edited


Once a template has been defined it can be edited (pencil icon), duplicated (copy icon) or deleted (trash can icon).


New templates can be added by clicking on the Add button (the plus icon in the top right-hand corner) and this will open the create page shown below.

Details Section

Template details section

There is a Create Issues section for every issue the template needs to create. The examples above have two different issues to create but you are free to define any number you like as long as you have at least one.  Occurrences of question marks in a circle are help for the field to the left of the question mark.  Hovering over this will give you helpful information about the field.


The following fields are available in the Create Issue sections:

  • Summary: the summary of the Issue.  You can refer to parent fields here by using one of: ${Summary}, ${Description}, ${Type}, ${Assignee}, ${Reporter}, ${Priority} or to a custom field, i.e. ${My Custom Field Name}.  If no value is present then the word null show unless an ! is placed after the $ symbol (i.e. $!{Description} will show the description if it is present otherwise it will show nothing). Field references are case sensitive.  If this is a Repeating Template (see below) then you can refer to the repeated field value by using ${RepeatItem}

  • Assignee: The user that the issue will be assigned to.  You can also refer to the parent issues reporter or assignee by entering ${Reporter} or ${Assignee} respectively.

  • Components: The component(s) that the issue should have.

  • Description: a description of the Issue.  You can also refer to the same fields as defined for the Summary (i.e. ${Reporter})

  • Due Date: either the word today (for the day the Sub Task is created), a date (in the format YYYY-MM-DD) or the number of days, weeks and months from the day the Sub Task is created (i.e. 1m 2w 3d for one month, two weeks and three days, 2d for two days ...)

  • Original Estimate: the number of minutes, hours, days and weeks (i.e. 3d 4h, 1w 10m ....), as a percentage of the parent's original estimate (20%) or as a multiplier of the parent estimate (*0.25)

  • Fix Versions: The fix versions for this issue.

  • Issue Type: Defined the issue type for this issue 

  • Labels: Any labels you wish to add

  • Priority: one of the pre-defined priorities for an Issue

  • Reporter: Start typing the user's name and a selection of matching names will appear.  You can also refer to the parent issues reporter or assignee by entering ${Reporter} or ${Assignee} respectively.
  • Custom Field: you can specify any custom field (up to five total) of type single-line text, multi-line text, number, and single select item. The value for that selected field can be specified.

  • Project Key: The key of the project this issue belongs to (can't be used for subtasks).


You can add more fields to set by selecting them from the "Fields to display" dropdown menu. You can also remove fields by clicking the X next to their name.  The fields in each Create Issues section can be different for each Create Issue.

The fields that are showing don't necessarily have to have values in them. In the example above the second-row description and assignee fields are visible but empty.  This allows the user, using the template to create Sub Tasks, to easily enter the reporter with minimum fuss.

Copy From Parent

The details section of the template has a name that will help identify the issues to create that belong to it, an "Add current user as watcher" checkbox to add the current user as a watcher for every issue created and optional documentation fields. Clicking on the "Show more documentation options" link will show the description and documentation link fields.

Create Issues Section

Template create issues section
Template create issues section

This section allows you to select fields that you want copied from the parent issue.  You can select as many fields as you want. For the example above just the Fix versions and Labels fields will be copied from the parent Issue to all of the newly created issues. The fields to copy also include a list of custom fields. The only time these fields will NOT be copied is if the field's value is set in the Create Issues section that is being created.

Cascade Template

Template copy from parent section

The Cascade Template section allows you to create another templates issues for each of the issues created in this template.  This functionality is only available for creating linked and unconnected issues because the cascaded template has the same relationship (linked or unconnected) as the parent template.


For example, if you have two templates, A and B.  Template A will create two issues with the summaries Development and Testing.  Template B will create a single issue with a summary Security Check.  If template A has a cascade template of B then if template A is created as linked issues then each of those linked issues (Development and Testing) will also have new linked issues from template B (Security Check).  So a total of four issues are created.

Repeat Template

This section allows you to repeat the template creation based on the selected field (Components or Fix Versions).  So if your template has two rows (two issues to create) and you specify that you want it repeated for Components then two issues will be created for each component that the issue has (i.e. if the template has three issues and there are two components then a total of six issues will be created).

If "Set Repeating fields value in Issue" is checked then the current field value being iterated over will be set in the issue created (i.e. if the template has one issue definition, a repeating field of Fix Versions (V1 and V2) and the parent issue has two fix versions then two issues will be created where the first issue has a Fix version of V1 and the second of V2).

Template repeating section

Global Templates


Global templates are templates that can be used in any project (as long as they are specified as visible in projects) and when creating sub tasks, linked issues or Epic issues as part of a workflow transition.  The global template page can be navigated to through the menu at the topmost Jira menu (click on the Jira symbol in the top left of the screen) and clicking on the STM Global Templates option.


Clicking on the Global Sub Task Template screen will navigate you to the following screen.


Adding a new Template will show the page below.  This is almost identical to the project template dialog except for the "Show in Issues for Bulk Create pages" checkbox.  If this is checked then the template will be shown when creating bulk sub tasks, linked issues, unconnected issues or Epic issues.  Either way, global templates are always available for creating as part of an executor (see below).

Apart from the addition of the checkbox, all functionality is identical except that select dialogs such as issue types, priorities, etc will show every possible value.  This is because global templates are not associated with a particular project and hence cannot show a subset of these lists.


Because these lists show all possible selections the template being created as part of a workflow transition may cause an error.  More about this is described in the Workflow section.

Global template example

Creating/Deleting Bulk Sub Tasks/Linked Issues/Epic Issues

To create Sub Tasks, create Linked Issues, create Epic Issues, create unconnected issues, delete Sub Tasks, delete linked issues or delete Epic issues go to the Issue that will be the parent, click the More dropdown button and select the appropriate menu item.  Epic Issue creation and deletion are only available if you are running the "JIRA-Software" version of JIRA.

The following dialog will be displayed.  The difference between the Sub Task and Epic Issue dialogs is the title and the Issue Types that can be selected.

This dialog is very similar to the one for creating Sub Task or Epic Issue templates.  The main difference is instead of a template at the top you select list of all templates for this Project and an Issue Type select to specify the Issue Type of the new Sub Tasks / Epic Issue.


There are two ways of using this dialog: creating Issues from a template or creating Issues from scratch.


Create bulk Issues from a template

To create bulk Issues from a template the user selects a template from the Template To Create drop down.  The drop down has a list of all templates the belong to a Project.  Once a template is selected then all of the Show Fields, Sub Task list and Copy From Parent fields are displayed for the Template.


The minimum a user has to do is select an Issue Type and press Create Sub Tasks / Epic Issues.  Optionally the user can also customize the fields used, enter or change the value and even add new Sub Tasks / Epic Issues if they wish.  Once all changes are made then the Create button can be pressed.  Any changes performed in this screen are NOT updated to the template.


Create bulk Issues manually

To create bulk Sub Tasks / Epic Issues manually select "Don't use Template" from the Template To Create drop down.  This will clear all the Show Fields, Sub Tasks list and Copy From Parent.  The user can add details the same as they could do from the Template screen.  Once they have finished they just hit the Create button.


Repeating Templates

If you select "Repeat this Template" then you will be able to select which fields contents you will be able to iterate over, Components of Fix Versions.  

Once the field has been selected you can specify if the repeating field values are set individually on the new issues.  Under this is the list of components/fix versions (from the current issue) that will be iterated over (all checked by default). 

So for the above example if there is one issue defined in the template and all three components checked then three issues will be created, one with a component of Backend, another with Front End and the final one with Proxy Server. 

Delete Bulk Sub Tasks

To delete bulk Sub Tasks select the "Delete Bulk Sub Tasks" menu item.  That will display the following dialog.  Check the boxes of the Sub Tasks you want to delete and press "Delete Sub Tasks".  You can also click on the circle containing three dots to display more information about the Sub Task.

Delete Linked Issues

To delete bulk linked issues select the "Delete Linked Issues" menu item.  That will display a dialog similar to the one shown in "Delete Bulk Sub Tasks".  Check the boxes of the issues you want to delete and press "Delete Linked Issues".  You can also click on the circle containing three dots to display more information about the issue.

Delete Epic Issues

To delete bulk Epic issues select the "Delete Epic Issues" menu item.  That will display a dialog similar to the one shown in "Delete Bulk Sub Tasks".  Check the boxes of the issues you want to delete and press "Delete Epic Issues".  You can also click on the circle containing three dots to display more information about the issue.

Manually creating a template in the issue page

Project Executors - Automatic template creation

To automatically create bulk Sub Tasks, create Linked Issues or create Epic Issues you need to create an Executor.  The Executor screen is available as a Project tab (go to the project -> Add-ons -> STM Executors) The image below show the screen where executors can be added and edited.

Executor (when enabled) will create issues automatically, based on the specified template and criteria.  If you don't want a template to run then edit the Executor and uncheck the Enabled checkbox.

Once an Executor has been defined it can be edited (pencil icon), duplicated (copy icon) or deleted (trash can icon).  These icons show when you hover over the an Executor

New Executors can be added by clicking on the add button (plus icon, top right-hand corner) and this will show the add Executor page shown below

List of project Executors
Setting the name and enabled of a new Executor
specifying when the executor will run when transitioning
Select when the executor will be run

To start with you are asked to enter the name of the Executor and whether it is enabled or not.  Click on the Next button to go to the next page.

You now need to decide when the executor will run, when the issue is created or when it is transitioned.  Click on "On Create Issue" or "On Transition" to continue.  For the purposes of this documentation we clicked "On Transition"

For On Transition we need to enter the To Status of the transition and optionally select the From Status.  We then click Next.  When Next is clicked we get the option of either creating a Condition or Action.

Choose to add a condition or action to the executor

For this example we will add a condition to the Executor.  Clicking on Condition will give us the choice of either testing a fields value or testing who is the current user.  For this example we will choose to test a fields value.

Choose which type of condition to use

We add a test to make sure that the Issue type is an Epic and click Next.  We get to choose the between another Condition and an Action.

Test the value of a field in the executors condition

This time we choose to create an action

Create a Sub Task for the Executor
Choose either a condition or action

Now we get presented with a list of different actions to perform.

Actions to perform for an Executor

We then select the template to use and the default issue type.  After that, we click save and return to the Executors page.  

NOTE: The items in the left-hand panel can be clicked on to change which part of the Executor you are looking at.

We choose to create a Sub Task.


Global Executors - Automatic template creation

Global Executors are very similar to Project Executors.  The only difference is that you have to either say that it applies to all projects or you select which projects it will apply to.  See Project Executors, above, for the general usage of an Executor. 

The screenshot below shows the difference for the Global Executor.  This includes a selection of whether this is for all or selected projects and if it is for selected projects then which ones.

Is the global Executor for all or selected projects
Enter the selected projects this Executor is for

Workflow - Automatic issue creation

NOTE: Workflow post functions are one means of automatically creating issues from templates, the other being Executors.  Executors were created to be easier to use while providing more functionality than the post functions currently provide.  Also in the future Executors will be getting more functionality added that is not able to be added to post function.  For that reason please use Executors to get the most out of this plugin (see the section above).


Sub tasks can be created automatically as part of a workflow transition.  This is done by creating a custom post function for a workflow transition.  See the two URLs for more information on doing this:



When in a workflows transition screen, click on the Post Functions tab and then the Add post function link.

Click on the "Add post function" link.  The following screen will be shown.  Select "Sub Task Creation" and then click the Add button.

Next, the parameter screen is shown.  Here you select the global template you want to use, the default issue type to use and any conditions.  Only global templates can be selected here because workflows can be used across multiple projects.  The optional conditions are either Test Field Values (equating a JIRA or custom fields to be equal or not equal to a value) or current user check (saying that the current user equal to not equal one or more users).  Conditions are evaluated at the time of the transition and the Sub Task, Linked Issues or Epic Issues are created if all of the conditions are true.

Click the add/update button once you have entered the template and issue type.  The post function will now be added to the transition.

Important: At this stage, the workflow is still in draft mode.  You need to publish the workflow before the transition can be used to create the subtasks.


Automatic issue creation - In Action

When an Issue completes a transition that creates sub task(s) / linked issue(s) / Epic issue(s) through either an Executor or a workflow post function a message box is displayed to inform the user that processing is occurring in the background.  STM will keep checking in the background to see if the sub task(s) / linked issue(s) / Epic Issue(s) have been created.  When they are created then the Issue is refreshed to display them and a message is displayed to show that they have been created.  Below are examples of the pending and created messages

If an error occurs during the creation process then an alert dialog will be displayed telling the user what happened.

As well as being displayed in the popup dialog all STM workflow errors are also available in a project administration (see below).


Permissions Error: If you get errors saying that the user does not have permission to view or edit an Epic then you will need to give edit and viewing permission of the app's user (addon_com.redmoon.subtaskmanager.jira).


Any errors that occur during the creation of sub tasks or Epic Issues in a workflow transition can be viewed under the "STM Errors" tab in a project administration screen.  Details are kept for up to two weeks after the error occurs (at which time they are deleted).


Bulk Update of Issues from an Issue filter

In each project, there is an issue filter that allows you to get a selection of issues using either a pre-defined filter (i.e. My Open Issues...) or JQL.  The filtered list can have a template applied to each issue to create sub tasks, Epic issues or linked issues.  To do this select the appropriate option from the export menu (top left-hand corner of the screen).

This will take you to a template selection screen.  Below is the linked issue template selection screen.


This screen looks almost the same as when you manually create bulk linked issues.  The only difference is the "Issues to Process" field which lists the keys of all the issues from the issue filter screen.  You can remove or add issues keys by clicking to the right of the existing keys.  Please see the create bulk sub tasks section above for details of using the rest of this form.


For the Repeating Template section, all components/fix versions for the first issues project are displayed.  If you are wanting to use a Repeating Template then you will need to make sure all of the issues to process are from the same project.


NOTE: The only template shown are global templates.  This is because the filter screen can show issues across multiple projects.


When you have finished selecting a template or manually setting one up just click the Create Sub Tasks button to start creating issues.  This will hide the screen above and show each Issue key, the processing progress and any information, such as issues created or errors.  When the example above was run and was completed it looked like the screen shown below.

Creating linked issues or Epic issues looks very similar to that shown above and so won't be shown here.



Change Log


The change log page allows you to audit changes that have been done to templates in the last three months.  The example below shows seven templates of which two have audit data.  The audit data also includes deleted templates.

Note: Audit data is only collected from the date this release was installed.

Create Template Access

The configuration screen allows you to define access to the global and project template screens.  


For the global template screen, system admins always have access.  For the project template screens, project admins always have access.  Use one of the two fields (shown below) to specify which additional users will also have access by entering one or more user groups.  All users in those groups will then have access.

Language Support

NOTE: Translations apply to all text EXCEPT the menu text, tab text, and panel heading text.

The Langauge Support section allows you to choose a language to get the App to choose for you.  This plugin comes with two languages pre-installed: English and German.

STM language page