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 is used to automatically create 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.
Conditional copying attachments
Conditional copying attachment (controlled by custom field) is always only checked for the issue in transition regardless of whether the issue in transition is a source or destination.
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
When choosing a user account to run a post function, the specified user account must have the appropriate permissions to perform the actions, such as creating an issue or adding a comment.
If JSU determines that the specified user has insufficient permissions, it executes the rule using the JSU Add-on user. This is displayed in the Execution Log as a success and includes a warning.
JSU can’t determine if the specified user is missing necessary Jira global permissions. In this case, the rule runs using the specified user. If the run encounters a Jira error, it will fail. This is displayed in the Execution Log with a permission error.
JSU Add-On User (default)
The JSU Add-On User account is automatically added to an instance when JSU is installed and already has the required permissions to perform all actions across JSU post functions. If the permissions haven’t been manually removed from the JSU Add-On User, it should not impact its success as the Perform as User instead of another account.
If you don't specify a different option, the transition on the related issue is performed as the JSU Add-On User with its associated permissions. This option is useful for testing, and you can confirm the action in your issue activity.
When the JSU Add-On User makes changes to issues, you can see the changes in the Activity section of the issue:
Initiating User
The transition on the related issue is performed with the same user who triggered this post function on the origin issue. That user must have the necessary permissions on the related issue. In some restrictive setups, a user might not be allowed to perform the action or might not have permission to view the relevant project.
Choose user
Use this option to specify a different user account that has been granted the necessary permissions. Usually, this user account is assumed to be only technical (impersonation), with broad permissions, and not used by individuals to log into Jira.
In combination with the Permission condition in native Jira, or the User Is In Any Users condition from JSU, you can hide a transition from all users that do not have permission to execute it.
Initiating/Specified User
If you configure your post function for either the initiating user or a selected user, the relevant issue fields must be included in the associated issue screen.
For example, if you create a rule that updates a field in a related issue, the field must be included in the target issue Edit screen. Similarly, if you define a rule that creates a new issue, or copies a field to a new issue, the field must be included in the Create screen.
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.
On adding the ‘Create Linked Issue’ post function to the ‘In progress’ transition, configure the fields you prefer with 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 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 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 set of operations!