JIRA Software : Available features in federating JIRA
What are the available features in federating JIRA?
サーバー版 / クラウド版
The ability to have Atlassian products work together is one of the strongest features of JIRA, Confluence, and the entire Atlassian stack. The best example is to list JIRA issues within a Confluence page. This same functionality also enables to integrate autonomous JIRA instances. The JIRA servers, do not need to run the same version as long as all versions contain the Application Links functionality. This makes interoperability in a diverse landscape (e.g. see reasons to federate, "Access to new features") a lot easier.
The goal of application links is to make inter-instance linking and integration of issues as easy as inter-project integration within the same instance! So after you set up an application link between your JIRA instances, the integration functionality described below becomes available:
Activity streams not only show updates from the instance you are on but also from connected JIRA or other Atlassian product instances (e.g. Confluence or FishEye). For example, if two companies working together on a project and linking their JIRA instances can update the new status changes of work through a unified activity stream.
You can add Gadgets that draw their data from another linked and trusted JIRA instance to a JIRA dashboard. This enables a unified reporting outline of all relevant instances. At Atlassian, for example, we utilize information radiators to show real-time reporting across our internal and external JIRA instances. Next to the standard gadgets, you can also add more gadgets. The applications are endless – from just one gadget that reports on a specific metrics of another project in another instance, to having one central instance in your federation that runs reporting of all projects in all JIRA systems!
Linking issues are important to connecting relevant JIRA issues. With remote links, you cannot only track dependencies and other relations of issues to other local projects but remote projects in other instances as well. See our example about how we connect issues in JAC (JIRA.Atlassian.com) with internal development tickets in our JDOG instance.
You do not have to remember the addresses of your Atlassian products anymore. The Application Navigator header allows for fast switching between JIRA instances, as well as other Atlassian products working together.
Often, you will have a project in an internal JIRA instance for to develop a certain product and then a project in an external instance for the support of that product. With project links, you can easily connect these two projects. For example, an activity stream in JIRA1 that points to JIRA2 will automatically show related updates of a connected project.
6.JIRA Issue Copy (by Atlassian Labs, not supported)
Atlassian Labs has developed the JIRA to JIRA Issue Copy, which allows users to copy an issue from one JIRA instance to another. It is still in Atlassian Labs and available on the Atlassian Marketplace. It has a cleaner and easier to understand user interface, and supports more custom configurations and improvements in the user matching algorithm. Note that Atlassian does not support this add-on, and although it may work for you now, we don't recommend building it into a process that you rely on because of its Atlassian Labs status.
Although searching across multiple instances is not part of an out-of-the-box JIRA installation, you can achieve it through ALM's JIRA Client. This plugin is a desktop application designed to enable offline work with JIRA. It lets you set up connections to an unlimited number of JIRA instances and once you set up this connection, search queries are executed automatically across all the various systems.