| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, you can find the documentation heresee our JSU Cloud documentation. |
| Table of Contents |
|---|
| Info |
|---|
The 'Create a Linked Issue' feature is available from JSU 2.0 |
...
Create Linked Issue is a very powerful post functionsfunction. It has several sections for its configuration. See also further down.
Precondition
| Include Page | ||||
|---|---|---|---|---|
|
...
The configuration then has several sections, as describe described in the following sub chapterssections:
Function Execution Control
...
| Info |
|---|
If you use 'Move Attachments added during Transition' it is important that the 'Create Linked Issue' Post-Function is before JIRA Post-Function 'Update change history for an issue and store the issue in the database'! |
| Warning |
|---|
Due to a Bug in Jira JRASERVER-65939, 'Copy or Move Attachments' functionality, which are is added through a Transition Screen, does not work in Jira 7.5.x & 7.6.0. If you require this functionality, please upgrade to minimum Jira Version 7.6.1! |
...
Here you must configure some always mandatory fields for an issue. These are some real basic field of JIRA. Be aware that your JIRA 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 thus this post function). However you might overwrite them again later with Copy from the Origin Issue to the New Issue
...
A new issue will be created in this same project
Project variables
If you use the workflow with the 'Create a Linked Issue' post function in several JIRA projects, you might choose 'Project variables'. You then can configure in each of those JIRA Jira project a different target project for the newly created issues. For more about project variables see Project Variables.
...
The new issue will be created with the same user, who triggered the transition on the origin issue. If that user does not has have the necessary permissions in the target project he will get an error. Also if some validators prevent the creation of the new issue.
Selected Project
A new issue will be created in the selected project
| Anchor | ||||
|---|---|---|---|---|
|
A new issue will be created in a project which is defined in the selected custom field. Here available are fields of types: single select, radio buttons, project pickers
...
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
...
However, in some restrictive setup setups that 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 which 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 persons.
This Issue will be related via
Since JSU 2.1.0 the Create a Linked Issue 25680449 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.
...
| Anchor | ||||
|---|---|---|---|---|
|
Issue type can be set to:
...
Defined by custom field selection
Similar to Target Project an issue type can be defined by value selected by user in a dedicated custom field.
Be aware, that the issue type you provide in this custom field must be available in the target project.
The user will be able to select which issue type should be created.
As Jira administrator you also have to create this custom field (in the sample screenshots: Destination Issue Type). Take care of correct values of this custom field. These values have to match with the issue types available in the target project.
Configure Fields
In JSU you can define configurations in order to modify fields on the origin and new issue, only available for 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
Choose your Field Configuration
...
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.
...
On adding the "Create Linked Issue" post-function to the "In progress" transition, configure the fields you prefer with the help of the 3 three New 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 value of a field in a new linked issue
...
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 database.". As the create transition behaves differently than other transitiontransitions, the copying and/or moving attachment and copy field within same issue functionalities are not available in this case.
In any case, if you use 'Move Attachment' (see bellowbelow) you must position the post function before 'Update change history for an issue and store the issue in the database.'
...