--- title: "Related issues" canonical: "https://support.appfire.com/space/JSU/12682322/Related%20issues" format: markdown --- > Macro (aura-html) > ℹ️ This content is for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud [documentation](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518756). Several JSU post functions let you define the scope 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 subtask. ### Types of issue relations ![Portion of a JSU post function configuration page showing the options described on this page.](media://a7f83ece-5a36-48c8-b9a9-8887da790b54) The related issue is determined by one of the following Jira concepts: - **Issue link** You can define the link type to define which issues will be affected by the post function action. You can define `ANY` if you want the action to be performed on any linked issues. - **Parent / Subtask** The related issue is either the parent or subtask of the origin issue. - **Epic / Issue in** **Epic** 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. For help with writing the JQL query, see [JQL reference](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682093). See our [JQL use cases](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12681740) for some examples. ### Issue in Transition *Issue in Transition* refers to the issue for which a workflow condition is checked, a workflow validator is examined, or a workflow post function is performed. It is the issue that triggered a workflow condition/validator/post function to be executed. ### Source and Destination Some post functions, for example, the [Copy Value From Other Field](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682498) 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 written to the destination issue. Other workflow modules do not have source and destination; you define the issue relation that will apply to that workflow module. For example, [Create a Linked Issue](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682165) will just create a new issue and then connect it with some Issue Relation to the issue in transition. ### Restrictions - [Copy Value From Other Field](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682498) post function: There should be only 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.) - If you use [Create a Linked Issue](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682165) 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 mentioned must be within the options to configure the issue relation. In case of problems, the workflow rule will still run, but a message will be entered in the log file. See [Troubleshooting](https://appfire.atlassian.net/wiki/spaces/JSU/pages/12682250) for how to turn on full logging for JSU. This is recommended while you test any new workflow configuration.