Workflow - Automatic issue creation

Post functions are deprecated, please do not use them.  Use Executors for all creation / updating and transitioning of issues. Post Function will only be available to legacy users.

To use the templates you will need to use the plugins post functions.  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.

This will display a list of post functions, including the five shown below.

Select the required post function that you require and click Add.  Next the parameter screen is shown.  This will be broken down into the individual post function types: Epic Issues, Linked Issues, Sub Task and Update Issue.

Epic Issues

In the Add Parameters screen you need to select the template you want to use (from the Create Issue Template tab), select the default issue type to use (this can be overridden in the template) and specify any conditions.  At the time of transition the conditions are checked and the Epic issues are only created if all conditions are true.  There are field value and current user conditions.

Test field value allow you to check if a JIRA or custom field has or doesn't have particular values (see examples below).  The current user condition checks to see the current user is equal or not equal to the list provided.

Once everything is completed click add.  This will take you back to the list of post functions with the new Epic issue post function added.

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 sub tasks.

Linked Issues

In the Add Parameters screen you need to select the template you want to use (from the Create Issue Template tab), select the default issue type to use (this can be overridden in the template), select the type of link you want to create and specify any conditions.  At the time of transition the conditions are checked and the Linked issues are only created if all conditions are true.  There are field value and current user conditions.

Test field value allow you to check if a JIRA or custom field has or doesn't have particular values.  The current user condition checks to see the current user is equal or not equal to the list provided (see Epic Issues above).

Once everything is completed click add.  This will take you back to the list of post functions with the new Epic issue post function added.

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 sub tasks.

Sub Tasks

In the Add Parameters screen you need to select the template you want to use (from the Create Issue Template tab), select the default issue type to use (this can be overridden in the template), select the type of link you want to create and specify any conditions.  At the time of transition the conditions are checked and the Sub Task issues are only created if all conditions are true.  There are field value and current user conditions.

Test field value allow you to check if a JIRA or custom field has or doesn't have particular values.  The current user condition checks to see the current user is equal or not equal to the list provided (see Epic issues above).

Once everything is completed click add.  This will take you back to the list of post functions with the new Sub Task issue post function added.

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 sub tasks.

Transition

In the Add Parameters screen you need to select the template you want to use (from the Transition Template tab) or use the "No template, use the same transition as the parent" option.  Next select child type (Linked Issues in this case) and the Link Types whose issues you want to transition.  Finally you can optionally select conditions to narrow down the issues this transition applies to.  At the time of transition the conditions are checked and the transitions are done only if all conditions are true.  There are field value and current user conditions.

Test field value allow you to check if a JIRA or custom field has or doesn't have particular values.  The current user condition checks to see the current user is equal or not equal to the list provided (see Epic issues above).

Once everything is completed click add.  This will take you back to the list of post functions with the new Sub Task issue post function added.

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 sub tasks.

Update Issue

In the Add Parameters screen you need to select the template you want to use (from the Update Issue Template tab), select the default issue type to use (this can be overridden in the template) and specify any conditions.  At the time of transition the conditions are checked and the issue will only be updated if all conditions are true.  There are field value and current user conditions.

Test field value allow you to check if a JIRA or custom field has or doesn't have particular values.  The current user condition checks to see the current user is equal or not equal to the list provided (see Epic issues above).

Once everything is completed click add.  This will take you back to the list of post functions with the new Update issue post function added.

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 sub tasks.

Redmoon Software

Site Designed: