Page Comparison

...

Several of JSU's workflow

...

post functions have the option

...

to define the scope of

...

related issues.

...

For example, instead of copying of copying a field within an issue during a post function, you might choose to copy it to a sub-tasksubtask.

...

Types of

...

issue relations

Related issue will be found issues are identified by one of the following Jira concepts:

• Issue

  Link
  

  link: You can define the link type to define which issues

  exactly

  will be

  affected

  modified by the operation.

  
  

  If the post function includes the link type

  is 

  is ANY option, the operation will be performed on any linked issues.

• Parent / Sub-Task

  
  

  : The related issue is either a parent or

  sub-task of each other

  a subtask of the issue.

• Epic / Issue in Epic

  
   This is only applicable, if you have Jira Software installed.
  

  : The other issue is either

  the

  an epic related by an epic link, or it is part of an epic. This is only applicable if you have Jira Software installed.

• JQL

  
  

  : A JQL query will be executed to

  find

  retrieve the issues

  , which

  that will be

  affected

  modified by the post function. You can use some placeholders in the JQL query, which will be replaced with the current field values of the issue in transition. For tips on writing the JQL query

  please follow the instructions on 

  , see JQL Reference

   .
  Also see our 

   or our JQL Use Cases for some examples.

Issue in

...

transition

We use the term 'Issue in Transition' when we refer refers to the issue for which a workflow condition is checked, for which a workflow validator is examined, or for which a workflow post function is performed.Or ; in other words, that issue , which triggered a workflow condition/validator/post function to be executed.

Source and

...

destination

For example, the Copy Value From Other Field Post-Function allows post function allows you to define the issue in transition as the source or destination of the copy operations, while you define the other end with an issue relation.
The field value will is then be read from the source issue and be written to the destination issue. Other workflow modules post functions do not have source and destination. So ; you just simply define the issue relation , which will apply for that workflow module.
For example that applies to the post function. For example, the Create a Linked Issue Post-Function will just create post function creates a new issue and then connect it with some Issue Relation connects it through an issue relation to the issue in transition.

Restrictions

Please use some common sense what can and what cannot work.

...

Related issues limitations

While we try to execute as many configurations as possible, there are some restrictions you should keep in mind.

...

• Copy Value From Other Field

Post-Function there

• post function: There should be only

1

• one source issue. Otherwise, it is

not clear

• unclear from which issue the value

will

• should be read.

(

• The current implementation will

just pick

• simply select one of them and ignore the rest

. Which one is not defined - sort of random

• .

)

• If you

  use 

  use the Create a Linked Issue

  Post-Function to

  post function to create a new

  sub-task

  subtask, you must also configure

  this

  the post function to create the new issue as an issue type of a

  sub-task and make sure the

  subtask. The target project

  is

  must be the same as the one

  of

  for the issue in transition

  .

...

• .