Page Comparison

Several of JSU's workflow modules provide the option the post functions let you define the scope of the module on for some related issues.
For example, instead 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

...

The related issue is determined by one of the following JIRA following Jira concepts:

• Issue Link
  You can define the link type to

  defined

  define which issues

  exactly

  will be affected by the

  operation.
  Since JSU 2.2.0, we introduced the value ANY. The operation will

  post function action.
  You can define ANY if you want the action to be performed on any linked issues.

• Parent / Sub-Task
  The related issue is either the parent or

  sub-task of each other

  subtask of the origin issue.

• Epic / Issue in Epic
  

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

  The other issue is either the epic, related by an epic link, or it is part of an epic. This is only available if you have Jira Software installed.

• JQL
  A JQL query can be used to find the issues that will be affected by the post function. You can use placeholders in the JQL query that will be replaced with the current field values of the issue in transition.
  

  Image Added

  For help with writing the JQL query, see the instructions on JQL Reference. See our JQL Use Cases for some examples.

Issue in Transition

We use the term 'Issue in Transition' when we refer to thhe 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 It is the issue that triggered a workflow condition/validator/post function to be executed.

Source and Destination

For Some post functions, for example, the Copy Value From Other Field Post-Function allows post function allow 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 then be read from the source issue and be written to the destination issue.

Other workflow modules do not have source and destination. So ; you just define the issue relation , which that will apply for to that workflow module.
For example example, Create a Linked Issue will just create a new issue and then connect it with some Issue Relation to the issue in transition.

Restrictions

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

Some examples:

• Copy Value From Other Field

  Post-Function

  post function: there should be only

  1

  one source issue. Otherwise, it is not clear from which the value will be read. (The current implementation will just randomly pick one of them and ignore the rest.

  Which one is not defined - sort of random.

  )

• If you use Create a Linked Issue to create a new sub-task, you must also configure this post function to create the new issue as an issue type of a sub-task and make sure the target project is the same as the one of the issue in transition.

Some of these restrictions are mentioned as 'must be' within the options to configure the issue relation.

We try to perform whatever is possible. In case of problems, the workflow module will still run through, but write a message into is entered in the log file. See Troubleshooting for how to turn on the full logging for JSU. It might be a good idea to do this This is recommended while you test any new workflow configuration to make sure you're not missing any thing.