Skip to end of banner
Go to start of banner

Related Issues

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

Version 1 Next »

Several of JSU's workflow modules provide the option the define the scope of the module on 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-task.

Types of issue Relations

Related issue will be found by one of the following JIRA concepts:

  • Issue Link
    You can define the link type to defined which issues exactly will be affected by the operation.
  • Parent / Sub-Task
    The related issue is either parent or sub-task of each other.
  • Epic / Issue in Epic
    (info) 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.


Issue in Transition

We use the term 'Issue in Transition' when we refer to thhe issue for which a workflow condition is checked, for which a workflow validator is examined, of 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 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 will apply for that workflow module.
For example Create a Linked Issue will just create a new issue and then connect it with some Issue Relation to the issue in transition.

  • No labels