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

Compare with Current View Page History

Version 1 Next »

On this page

Use case

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.


Use case details
Condition
Validator
Post functionCreate issue
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 you system.
Parent issue

Current issue

The Bug will be created in the current project.

Summary
Sub-task related to %{issue.components}
A generic summary indicating that the bug needs to be classified.
Additional fields

Assignee

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

    %{system.currentUser}
The description links to the current issue key.
Run asCurrent 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