Page Comparison

...

...

...

...

Description

This post function will create a new issue. The new issue will be linked to the origin issue (the one, which triggered the 'Create a Linked Issue' post function).

...

See the Testing and Fixing Bugs use case for an example of how several of our customers are using this post function. The video on that page shows you the following sample configuration in action.

...

Create Linked Issue is a very powerful post function. It has several sections for its configuration . See also further downdescribed below.Image Removed

...

Precondition

The configuration then has several sections, as described in the following sections:

...

 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. 

Initial Mandatory Values for the new Issue

Here you must configure some always mandatory fields for an issue. Be aware that your Jira configuration might have additional required fields (you should set them with Copy from the Origin Issue to the New Issue.Image Removed

...

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

...

An administrator can create a field "Destination Project" with several different values which will represent project key (only capital letters) or project name (capital and small letters are supported) 

...

Create new Issue as User

If you don't specify anything here, the create operation will be performed under the same user, who triggered this post function on the origin issue. Thus that user must have the necessary permissions to create the new issue.

However, in some restrictive setups that the user might not be allowed to create new issues in the target project. He might not even see the target project!

With 'Create new Issue as User' you can specify a different user account that owns the necessary permissions. Usually, this user account is assumed to be only technical, with broad permissions, but not used to log into Jira by in life personsan actual person.

This Issue will be related via

Since JSU 2.1.0 the 12682147 Create a Linked Issue post function allows you the create new issues, which are connected not only with an issue link, but instead also in a parent / sub-task, as well as epic / issue in epic relation.

...

Defined by custom field selection

Similar to Target Project an issue type can be defined by the value selected by the user in a dedicated custom field.

...

The user will be able to select which issue type should be created.
As a Jira administrator, you also have to create this custom field (in the sample screenshots: Destination Issue Type). Take care of correct Carefully note the values of this custom field. These values have to match with the issue types available in the target project.

...

This chapter provides you with definitions of the basic terms in Configure Fields.

• 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

...

Choose your Field Configuration

...

The following operations are available:

• Copy to New

• Copy within Origin

• Set

Organizing Operations 

You can configure any number of configurations. They are executed sequentially.

...

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

Let's say you are a Hiring Manager and you are onboarding a new Marketing Assistant. 

Your tasks to complete the onboarding would then include 

1. Create new contract 

2. Order new computer

First, you create your origin issue which you’ll call Hiring a Marketing Assistant. Instead  Instead of manually creating linked issues and copying/setting field values, JSU’s  JSU’s New 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 New JSU operations:

1. Copy a field value from the origin issue to a new linked issue

2. Copy the value from one field to another field within the origin issue, and

3. 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 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  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. Put it in progress and see the magic of the JSU's new set of operations!

...

 You can use this post function in the create transition (transition leading to Status "Open"), but you have to make sure to position the post function after "Creates the issue originally" and before "Re-index an issue to keep indexes in sync with the database.". As the create transition behaves differently than other transitions, the copying and/or moving attachment and copy field within the same issue functionalities are not available in this case.

...

See the Use Case Testing and Fixing Bugs for a nice an example , of how several of our customers use it. The video on that page shows you the following sample configuration in action.

Supported Field Types