Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 47 Current »

JSU for Jira Cloud

This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server or on Jira Data Center, you can find the documentation here.


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).

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 how several of our customers are using this post function. The video on that page shows you the following sample configuration in action.



There are several ways in which preconditions can be evaluated in the context of a post function:
  • True (Precondition must be true to execute a post function)
  • False (Precondition must be false to execute a post function)

You can find more generic description of precondition here

Initial Mandatory Values for the new Issue

Here you must configure some always mandatory fields for an issue. These are some real basic field 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

Target Project

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

Since JSU Cloud 1.1.0 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 / sub-task, as well as epic / issue in epic relation.

See Releated Issues for more explanations on this topic (especially for creating sub-tasks).

Perform As User

If you don't specify anything here, the transition on the related will be performed with the same user who triggered this post function on the origin issue. Thus, that user must have the necessary permissions on the related issue.

However, in some restrictive setup, that user might not be allowed to do so on the related issue. He might not even see the project of the related issue!

With 'Perform As User', you can specify a different user account who has been granted the necessary permissions. Usually this user account is assumed to be only technical (impersonation), with broad permissions, and not used to log into Jira by any coworkers. 

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 the permission to execute it.

Issue Type

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.

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. 

Definition of Terms for the Configure Fields Objects

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

Click the "Add Configuration" button and insert the operation you want to execute.

The following operations are available:

Organizing Operations 

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

You can rearrange the configurations by dragging in 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.  


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 of manually creating linked issues and copying/setting field values, 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 3 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 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. Put it in progress and see the magic of the JSU new set of operations!

Asynchronous Execution

There is a fundamental difference between Jira Server/Data Center and Jira Cloud: In Jira Cloud post functions of apps are executed asynchronous as a 'background job'.
  • This means a post function will be executed after the transition has completed on Jira Cloud.
  • There is no guaranteed order in which several post functions are performed. They might be executed in a different order from the one you had set them up in Jira's workflow configuration. So you cannot rely on any result of a 'previous' post function. The order by which the post functions are executed might be different every time the transition is performed.
  • When a post function has a problem (due to misconfiguration or the current data of a Jira issue), the transition (and all other post functions) will be performed nevertheless.
  • The result of a post function might not be visible immediately in the browser.
  • There are no error messages displayed to the user.


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

Supported Field Types

In its different modules (especially those for workflows), the JSU app supports many different field types. System fields, as well as custom fields.

However you should be aware, that not all field types or all combinations are supported. We think we cover the most important field types and are still continuously adding and improving which, and how different field types are supported. But the one you need might not work (yet). 

We recommend that you test JSU with fields to see if it is compatible with your system. Our evaluation license gives you 30 days free trial. 

  • No labels