Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

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

Compare with Current View Page History

« Previous Version 6 Next »

On this page

Introduction

The Transition issue post function automatically creates a single standard issue or sub-task in any given project. The issue type can be selected from all available issue and sub-task issue types in the system (excluding next-gen projects). 

Additional field values can be inherited or manually set using parser expressions. 


The configuration

The table below lists all available parameters that have to (*) or optionally can be set in this post function.


ParameterDescription
Issue type *

The issue type of the issue to be created. The following options are available:

  • Selected issue type
  • Parser expression (standard issue type) ((info) expects an issue type ID or reference like %{issue.issueType})
  • Parser expression (sub-task issue type) ((info) expects an sub-task issue type ID or a reference like %{issue.issueType})

In case a sub-task is chosen, the respective parent has to selected.

Parent issue (only for sub-tasks) *

Choose the parent issue under which you want to create a sub-task. The following options are available:

  • Current issue
  • Parent issue
  • Selected issue
  • Parser expression ((info) the output has to be an issue key)

The parent issue is only shown when a sub-task is selected as issue type.

Project *

 The project the issue will be created in. It comes with the following options:

  • Current project
  • Selected project
  • Parser expression ((info) the output has to be a project ID or a reference like %{issue.project.id})

Please note that the project selection does not show up when the issue type is a sub-task.

Summary *Enter plain text and optionally use field codes, e.g. %{issue.summary}, to insert field values.
DescriptionEnter plain text and optionally use field codes, e.g. %{issue.summary}, to insert field values.
Additional fields

Optionally set additional field values. 

In the popup after clicking the Add button you can select to set the value in two ways:

  • Copy field from current issue (the value from the selected field will be copied over to the new issue)
  • Set field value manually (parser expression)
Run as

 Select the user that will be used to execute this post function (the issue creator). It can be chosen from one of the following options:

  • Current user
  • Selected user
  • Assignee
  • Reporter
  • Creator
  • Project lead
  • Parent's assignee
  • Parent's reporter
  • Parent's creator
Conditional execution

Enter a condition (a logical expression) using the expression parser syntax. 

You can even logically link and nest conditions in expressions as you like in order to map more complex conditions. 

(warning) The post function will only be executed if the condition is met (returns true.).





Purpose

This post function executes a specific transition on the selected issue or transition the issue to a selected status. Both, transition and target status, have to be available from the issue's current status.

Configuration

ParameterDescription (default values are shown in bold at the top of the lists)

Target issue

The issue to be transitioned. The following options are available:

  • Current issue
  • Parent issue
  • Parser expression ((info) expects an issue key)
Mode

Select the transition to be executed or the status to be transitioned to. You can choose between to options:

  • Execute transition
    Pick either a transition which is shown by name and ordered by workflows or a parser expression ((info) expects a transition ID)
  • Transition to status
    Pick either a status which is shown by name or a parser expression ((info) expects a status ID)
Delayed executionExecuting the post function will be delayed by the specified value in milliseconds.
Run as

 Select the user that will be used to execute this post function. It can be chosen from one of the following options:

  • Current user 
  • Selected user
  • Assignee
  • Reporter
  • Creator
  • Project lead
  • Parent's assignee
  • Parent's reporter
  • Parent's creator
Conditional execution

Enter a condition using the expression parser syntax. You can even logically link and nest conditions in expressions as you like in order to map more complex conditions. 

The post function will only be executed if the condition is met.

Related use cases

TODO