Link to new issue

Select a link type from drop-down to link the newly created issue to the current issue

. The default value is "is not linked to", which will not create any link.

Copy fields to new issue(s)

Specify the current issue

fields to be copied to the new issue(s)

.

Mode

• Only copy or set fields listed below: if If you select this option, only fields specified explicitly under the Set specific fields of new issue section will be copied or set on the new issue.

• Copy all fields that appear on the Create screen of the issue type to create, in the target project: if If you select this option, all fields that appear on the Create screen of the issue being created will automatically be copied from the current issue to the new issue, as if they were being input entered by the user on the Create screen.

• Copy all fields: if If you select this option, all fields that have a value on the current issue and that apply to the issue being created will be copied from the current issue to the new issue.

Set specific fields of new issue 

Set the field values of the newly created issue, regardless of the option selected under Copy fields to new issue(s).

• Summary

• : This added by default since it is required for any issue type.

• To add a Add field:  Select Select a field from the list of fields drop down and click onAdd.

• To Remove an added field : Click on Remove to remove a field.

• To Set a field value to add the respective field. Set the field using one of the following options: 

  • Copy value from current issue : Copies the field value(s) from the current issue.

  • Set to other field of current issue: Sets the field to the value of another field of the current issue. Say, to set the Reporter of the current issue as the Assignee of the newly created issues.

  • Set field value to: You can set  Set the field to a specific value, which can include Nunjucks annotations.
    For example: To set the Fix Version/s to 2.0, you can specify 2.0 in the value boxthe value box.

• Click the Remove icon to remove the respective field.

• Ignore fields that don't apply to the new issue

• : If you add a custom field(s) above that do not apply to the issue being created (because it is configured to apply only to certain issue types or projects), the post-function will fail (so you can pinpoint the problem).

• Select this option to ignore this error instead, which can be useful if you are creating multiple issues in different projects or of different types

• .

Copy comments to new issue(s)

Using Use this option you can to copy the existing comments/newly added comments of the current issue to the newly created issue.

• Don't copy any comment to the newly created issue(s): This is the default option. Select this option to not copy comments to the newly created issue

• Copy the transition comment to the newly created issue(s): Select this option to copy the comment added on the transition screen to the newly created issue.

• Copy all comments from the current issue to the newly created issue(s): Select this option to copy all the comments on the current issue to the newly created issue.

Add

Copy the transition comment to the newly created issue(s)

a comment to current issue

• Add a comment to the current issue

• : Select this option to add a comment to the current issue.

• Comment (displayed only when the previous option is selected): Add any simple text, e.g. This is a comment. You can also use Nunjucks annotations in the comment using variables. To find out more about the variables, see How to insert information using Nunjucks annotations.

• Comment visibility

  • Restrict to Group: Restricts the visibility of the comment to a specified group. When you select a valid group name in the Restrict to Group field, the comment will be visible only Select a group from the drop-down to restrict the visibility of the comment to the members of the specified group. For no restriction, leave the field blank.

  • Restrict to Project Role: Restricts the visibility of the comment to a selected project role. When you select a Select a project role from the drop-down Restrict to Project Role field, the comment will be visible only to the members of the down to restrict the visibility of the comment to the users with selected project role. For no restriction, leave the field blank.

  • Restrict to Internal (Jira Service Desk only): Restricts Select this option to restrict the visibility of the comment to the Service Desk Agents and Collaborators onlyCollaborators.

• Create comment as

  • Create comment as current user : The : Select this option to set the current user will be as the author of the comment created. This is the default value.

  • Create comment as add-on user: The  Select this option to set the add-on user will be as the author of the comment created.

  • Create comment as this user: Any user selected in this field will be the author of the comment created.

Multiple Issue Creation

By default, the Create issue post-function will create a single new issue, according to the settings above. If you want to create multiple issues at the same time, check the Create multiple issues option. You will then need to provide an iterator script that will control how many issues are created.

Iterator template

• •  Select this option to enable the associated drop-down. Select a user from the drop-down to set the specified user as the author of the comment created.

Multiple issue creation

Use this section to create multiple issues based on the settings you provide.

• Create multiple issues: Select this option to create multiple issues at once. Provide an iterator script to control the number issues to be created. By default, the Create issue post-function creates one new issue.

• Iterator (displayed only when the previous option is selected): Enter a Nunjucks template that must return a comma-separated list of values to iterate on. This can be either a comma-separated list of Strings, or a JSON array only if you check the "Iterator returns JSON" option. The post-function iterates over the list and creates one new issue per value. If configured, a new comment is also added to the current issue for each new issue created. 

Template returning a comma-separated list of Strings, or a JSON array only if you check the "Iterator returns JSON" option below. The post-function will iterate over the list and create one new issue per value. If configured, a new comment will also be added to the current issue for each new issue created. 

Template returning a comma-separated list of Strings

If the iteration template returns: jdoe,tblack then one issue will be created with the it variable containing"jdoe"and then another with the it variable containing"tblack". And if, in the configuration of the post-function, you are setting the "Assignee" field of the newly created issue to the following Nunjucks Template: {{it}} then the first issue will be assigned to jdoe and the second to tblack. And when you test the template the tester will return jdoe.

Examples:

• Bug,Task

• {{issue.fields["Multi-user Picker field"] | join(",","accountId")}} will create one issue per user in the Multi-user Picker field.

• {{range(1,5)}}will create 4 issues, with the it variable containing numbers from 1 to 4.

Template returning a JSON array

If the iteration template returns a JSON array: [ {"assignee":"jdoe", "summary":"Issue for John Doe"} , {"assignee":"tblack", "summary":"Issue for Tim Black"} ] and you select the "Iterator returns JSON" option, then you'll be able to use {{it.assignee}} as the value for the Assignee field, and {{it.summary}} as the value for the Summary field.

Examples

• {{"jira-administrators" | groupMembers | dump }} with "Iterator returns JSON" option selected will create one issue per user in the 'jira-administrators' group

• {{issue.fields["Multi-select field"]  | dump }} with "Iterator returns JSON" option selected will create one issue per selected option in the Multi-select field

After issue creation

If the iteration template returns: jdoe,tblack then one issue will be created with the it variable containing"jdoe"and then another with the it variable containing"tblack". And if, in the configuration of the post-function, you are setting the "Assignee" field of the newly created issue to the following Nunjucks Template: {{it}} then the first issue will be assigned to jdoe and the second to tblack. And when you test the template the tester will return jdoe.

Examples:

• Bug,Task

• {{issue.fields["Multi-user Picker field"] | join(",","accountId")}} will create one issue per user in the Multi-user Picker field.

• {{range(1,5)}}will create 4 issues, with the it variable containing numbers from 1 to 4.

Template returning a JSON array

If the iteration template returns a JSON array: [ {"assignee":"jdoe", "summary":"Issue for John Doe"} , {"assignee":"tblack", "summary":"Issue for Tim Black"} ] and you select the "Iterator returns JSON" option, then you'll be able to use {{it.assignee}} as the value for the Assignee field, and {{it.summary}} as the value for the Summary field.

Examples:

• {{"jira-administrators" | groupMembers | dump }} with "Iterator returns JSON" option selected will create one issue per user in the 'jira-administrators' group

• {{issue.fields["Multi-select field"]  | dump }} with "Iterator returns JSON" option selected will create one issue per selected option in the Multi-select field

Post-creation script

• Run a Nunjucks script after the issue(s) are created: Select this option to run a Nunjucks script after each new issue is created to make additional changes to the issue, such as adding a remote link or calling an external API. In scenarios where you use this script for setting issue field values, the respective value set during issue creation is overwritten.

• Script: Enter the Nunjucks script as needed.

After issue creation

Automatically navigate to the newly created issue: Select this option to automatically navigate the user to the new issue created at the end of the transition. This is applicable only

when the transition

is triggered from the View Issue page. 

Run As

Select one of the following to set the creator of the issue:

• Run as current user: The current user will be the user that creates the new issue.

• Run as add-on user: The add-on user will be the user that creates the new issue.

• Run as this user: Any user selected in this field will be the user that creates the new issue.

Conditional execution

• user

• Run as this user:Select this option to enable the associated drop-down. Select a user from the drop-down to set the specified user as the creator new issue.

Conditional execution

• Run this post-function only if a condition is verified: Select this option to execute this post-function based on the result of a Nunjucks template. See Conditional execution.

• Condition (displayed only when the previous option is selected): Enter the Nunjucks template as needed.

Delayed execution

Use case

A typical use case for this workflow is to create one or more issues during a transition. Consider a use case where you want to create a documentation ticket only if "Needed" is selected in the "Documentation ticket" checkboxes field. To configure this:

1. Add the Create issue post-function to the transition on whose trigger you want to create a documentation ticket

2. Select Documentation from the Project field.

3. Select Document from the Issue type field.

4. Select caused by in the Link to new issue section.

5. Add an appropriate Summary (such as Release documentation)

6. Select the conditional execution and write the following template

{{ issue.fields["Documentation ticket"] | find({"value":"Needed"}) != null }}

See here for more use cases.