On this page
Configuration steps
Definition of basic (required) parameters
Parameter | Value(s) / Steps to set value(s) | Notes |
---|---|---|
Issue type * |
| The issue type to be created is being set to Sub-task. The issue type must be present in your system. |
Parent issue | Current issue | The sub-task will be created under the current issue. |
Summary * | Escalation of %{issue.key} | A generic summary indicating that the bug needs to be classified. |
Description | This sub-task was automatically created because the parent issue %{issue.key} had a priority of High at the time of creation. In case doubts or concerns do not hesitate to contact %{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 user | The post function will be executed as the current user. |
Conditional execution | %{issue.priority} == "High" | The sub-task will only be created if the current issue (parent) has a priority of High. |
This is how it's done
<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
Where | Final configuration |
---|---|
Backend | |
Frontend |
Related examples
Use case No content found.