Create a Linked Issue Post Function
This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server or on Jira Data Center, see our JSU Server/Data Center documentation.
On this page:
|
Description
The Create a Linked Issue post function automatically creates a new issue. The new issue will be linked to the original issue that triggered the post function. Any number of fields can be copied to the new issue and within the origin issue.
Configuration
Infinite Loop Detection: An infinite loop can occur when executing the Create a Linked Issue post function. An infinite loop results in an endless cycle of issue creation and follow-up transitions following the triggering of the origin issue. When a loop is detected JSU will stop the execution and log an execution failure.
When using post functions that create issues or follow-up transitions, consider the outcome of the rule and the user permissions of your project teams. You can also use preconditions to restrict when rules are run to reduce the likelihood of causing an infinite loop.
Post functions in JSU Cloud are executed asynchronously and a post function will be executed after the transition has been completed. If you use the Create a Linked Issue post function on a Create transition, the newly created issue will create another issue, which will create another issue, and so on. This results in an infinite loop and JSU will stop the execution to protect your instance.
Precondition
Copy attachments
Use it to define configurations to copy or move attachments to the newly created issue.
Tip: You might choose 'Move Attachments added during Transition'. The user then adds some attachments on the transition screen of the origin issue.
However, since they are moved to the newly created issue, it appears as if they added the attachments to the new issue.
Initial mandatory values for the new issue
Use this section to configure the mandatory fields for an issue. These are basic Jira fields. Remember that your Jira configuration might have additional mandatory fields (you should set these using the Copy operation).
Additionally, the summary will always be copied from the origin issue to the new issue. The reporter of the new issue will always be set to the user selected in the ‘Perform as User’ option. However, you might overwrite them later with Copy to the New sub-function.
Target project
The target project can be set to:
Inside same project: A new issue will be created in this same project
Selected Project: A new issue will be created in the selected project.
This Issue will be related via
The Create a Linked Issue post function allows you to create new issues that are connected not only with an issue link but instead in a parent / sub-task, as well as epic / issue in epic relation. See Related Issues for more information.
Issue type
Define the issue type of the new issue. The issue type you select here must be available in the target project.
Perform as User
Sub-functions: choose your field configurations
In JSU you can define configurations to modify fields on the origin and new issue; only available for the Create Linked Issue post function.
Origin issue: Issue that triggered the post function
New issue: Issue to be created by the post function, which was triggered on the origin issue
To add a sub-function:
Select + Add Configuration to view the available operations.
Select Add for the required operation.
The following operations are available:Configure the fields as required. See an example setup below.
Organizing operations
You can configure any number of configurations; they are executed sequentially.
You can rearrange the configurations by dragging the line using the handle on the left.
You can also disable a configuration by unchecking the enabled flag next to the delete button. Your operation will remain on your configuration but will be ignored.
Example
As a Hiring Manager, you are onboarding a new Marketing Assistant. Your tasks to complete the onboarding could include:
Create a new contract.
Order a new computer.
First, you create your origin issue, which you’ll call Hiring a Marketing Assistant. Instead of manually creating linked issues and copying/setting field values, JSU’s set of Operations can help automate these tasks.
When adding the Create Linked Issue post function to the in progress, configure the fields you prefer with the 3 JSU operations:
Copy a field value from the origin issue to a new linked issue
Copy the value from one field to another field within the origin issue, and
Set the value of a field in a new linked issue
First, you can copy a field from the origin to the new issue. Let's copy the assignee of the task to the assignee of the subtask. Then, you can copy a value from a field of the origin issue to another field of the origin issue. We'll try it by copying the summary to the description and prepending it with a dash. Configure the last operation by setting a value for the summary of the new issue. We'll set it to Create contract.
When you are done with your configuration, select Add at the bottom of the page to save the post function. You can do the same for as many subtasks as you want to have automatically created. Finally, publish your workflow and go back to your issue. Move it to in progress and see the magic of JSU’s automation.