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

Compare with Current View Page History

« Previous Version 7 Next »

On this page

Use case details
FunctionCreate issue
Type

Use case description

This is one of the built-in usage examples and creates a sub-task, sets the summary based on the parent's component and sets the assignee to the current user.

Complexity

BEGINNER



Configuration steps

Definition of basic (required) parameters


ParameterValue(s) / Steps to set value(s)Notes
Issue type *
  1. Issue type: Selected issue type
  2. Value: Sub-task

The issue type to be created is being set to Sub-task.

(warning) The issue type must be present in your system.

Parent issue

Current issue

The Sub-task will be created under the current issue.

Summary *
Sub-task related to %{issue.components}
A generic summary indicating that the sub-task relates to the parent component.
Additional fields

Assignee

  1. Value: Set field value manually (parser expression)
  2. Expression: 

    %{system.currentUser}
The assignee will be set to the current user.
Run as *Current userThe post function will be executed as the current user.



This is how it's done


Screencast

<Screencast goes in here> Detailed instruction can be found here: https://www.decadis.net/confluence/display/XAPPSBRANDING/Screencasts+Framework

Use multimedia macro!



This is how it should look like


WhereFinal configuration
Backend

Frontend



Related examples