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

Compare with Current View Page History

« Previous Version 9 Next »

On this page

Use case details
FunctionCreate issue
Type

Use case description

When a story is approved, two sub-tasks for Development and QA will be created.

Complexity

INTERMEDIATE



Configuration steps

Definition of basic (required) parameters


First sub-tasks "Development"

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 *
Development of %{issue.key}
A generic summary indicating the purpose of the sub-task.
Description
This sub-task was automatically created because the Story and parent issue %{issue.key} has been approved.

In case doubts or concerns do not hesitate to contact [%{system.currentUser.displayName}|~accountid:%{system.currentUser}].

The description links to the current issue key.

The syntax used for the mention guarantees that a working user mention is added to the comment regardless of personal Atlassian account settings of the mentioned user.

Run as *Current userThe post function will be executed as the current user.
Conditional execution
%{issue.issueType} = "Story"
The sub-task will only be created if the current issue (parent) is a Story.

Second sub-task "QA"

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 *
QA of %{issue.key}
A generic summary indicating the purpose of the sub-task.
Description
This sub-task was automatically created because the Story and parent issue %{issue.key} has been approved.

In case doubts or concerns do not hesitate to contact [%{system.currentUser.displayName}|~accountid:%{system.currentUser}].

The description links to the current issue key.

The syntax used for the mention guarantees that a working user mention is added to the comment regardless of personal Atlassian account settings of the mentioned user.

Run as *Current userThe post function will be executed as the current user.
Conditional execution
%{issue.issueType} = "Story"
The sub-task will only be created if the current issue (parent) is a Story.



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