First of all, when you link issues you create bonds/associations between them no matter if those issues are located on the same Jira server or on different ones.
When do you need to link Jira issues? For example, some of your Jira issues may duplicate one another, or handling one issue may depend on resolving another. Here are the default link types offered by the latest Jira installations:
- relates to / relates to
- duplicates / is duplicated by
- blocks / is blocked by
- clones / is cloned by
The combination of issues allows you to:
- Generate a new related issue right from a known issue. You can do it in a service desk or current project your team is running.
- Connect an issue in Jira and a page in Confluence. Do it through building a link between the platforms.
- Associate an issue in Jira with any other web-based resource page.
Please note that you should have the necessary permission for the project allowing you to connect issues before you begin. Keep in mind that your administrator appointed for Jira will be able to personalize the kinds of connections you generate.
Now, you probably want to know how to optimize the process of linking issues in Jira. We have a great solution for you.