This post function is used to automatically create a new issue. The new issue will be linked to the origin issue (the one that triggered the Create a Linked Issue post function). Any number of fields can be copied to the new issue and within the origin issue.
Use it to define configurations in order 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 feels as if he added the attachments to the new issue.
Conditional copying attachments
Conditional copying attachment (controlled by custom field) is always only checked for the issue in transition regradless of whether the issue in transition is a source or destination.
Initial mandatory values for the new issue
Here you must configure some always mandatory fields for an issue. These are some basic fields of Jira. Be aware that your Jira configuration might have additional required fields (you should set them all by Copy Field Section).
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 who triggered the current transition (and thus this post function). However, you might overwrite them again later with Copy from the Origin Issue to the New Issue.
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.
A new issue type will have a particular issue type. Be aware, that the issue type you configure 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.
Configure the fields as required. See an example setup, below.
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.
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.
On adding the Create Linked Issue post function to the "In progress" transition, configure the fields you prefer with the help of the three 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 sub-task. 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 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, add your post function. You can do the same for as many sub-tasks 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 set of operations!