Page Comparison

Description

This post function creates a new issue, 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.

See the Testing and Fixing Bugs use case for an example of how some of our customers use this post function.

Configuration

...

Precondition

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

Function execution control

Here the idea is, that you have a checkbox custom field on the transition screen, so the user can control some of the functionality. For example a checkbox 'Create Bug?' might be configured as 'Custom Field that enables linked issue creation'. Only if it is ticked, a new issue will be created. Typically this checkbox custom fields won't appear in the normal screen of the issue. Also at the end you might set them back to the original (default) value (see Copy within the Origin Issue).

...

Mandatory values for the new issue

Here you configure the 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.

...

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 therefore this post function). However, you could overwrite them again later with Copy from the Origin Issue to the New Issue

Target Project

Target Project can be set to:

...

Workflow Name and Workflow Transition Number are optional.

Example

From project A, you might create new linked issues in project X. But from project B, you might create new linked issues in project Y. But both use the same workflow.

...

The new issue will be created with the same user who triggered the transition on the origin issue. If that user does not have the necessary permissions in the target project they will encounter an error. Similarly, if some validators prevent the creation of the new issue.

...

A new issue will be created in a project defined in the selected custom field. Available fields of types: single select, radio buttons, project pickers

Example

An administrator can create a field "Destination Project" with several different values which will represent the 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, the user might not be allowed to create new issues in the target project; they 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 for normal activity.

This Issue will be related via

The 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 / subtask, as well as epic / issue in epic relation.

See Related Issues for more explanation on this topic (especially for creating subtasks).

Anchor
issue-type-by-cf issue-type-by-cf

Issue Type

...

Issue type can be set to:

...

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

Configure

...

fields

In JSU you can define configurations to modify fields on the origin and new issue, only available for Create Linked Issue post function. 

Definition of

...

terms for the

...

configure fields objects

This section provides 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

Click Add Configuration and insert the operation you want to execute. 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 rearrange the configurations by dragging 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

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

...

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!

Position of the post function

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. You can add this post function several times in one transition.

Example

See the Use Case Testing and Fixing Bugs for an example of how some of our customers use it.

Supported field types