I quote:
Gadgets can be added to a dashboard that draw their data from another linked and trusted JIRA instance. This enables a unified reporting overview of all relevant instances. ...
... having one central instance in your federation that runs reporting of all projects in all remaining JIRA systems!
I have two linked Jira instances but I cannot find out how to draw data from both instances. e.g. I like to create a dashboard with a gadget showing all 'Major' issues raised in instance A and instance B. As the gadgets are based on search queries, which do not support selecting the instance to search into, I wonder how this can be achieved.
Kindly requesting advise.
Source: https://confluence.atlassian.com/display/ATLAS/Federating+JIRA+-+Managing+Multiple+Instances
Thank you Scott, this has been helpful. Although I am an admin I don’t see the “Add Gadget to Directory” or the “Gadget Subscriptions” options that Ryan sees on the “Gadget Directory” modal. I did some more digging with another one of our Jira admins who does see these options and it appears that you get these options only if you have the correct type of admin permissions.
The presence of the two JIRA systems in the app navigator (top left corner) doesn't necessarily mean that the systems are linked internally, for gadgets or for anything else. Did you register the external gadget feed from the other JIRA system? I assume you already have application links set up between the two instances as well?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Running into the same problem as there’s no apparent way to reference the gadget defined in another linked instance when you’re going through the workflow of setting it up. When you add the filter results gadget to a dashboard the user is never presented with an opportunity to pull in or reference the external gadget.
Here are the specific repro steps of the workflow.
Unsure if we’re not getting the option to link because of a config issue or a workflow misstep.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.